We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Support Kafka version 2.7 for IIDRCDC Kafka target
IIDRCDC supports Kafka as one of target source. At this time, IIDRCDC currently supports Kafka version 2.4 library to connect to Kafka.
This request is to add Kafka version 2.7 and higher level support for IIDRCDC.
Reasoning is below.
We are looking for Kafka v2.7 or later as it will be a match with the Kafka server version 2.7. Kafka does have backward compatibility with version. But Issue is the Messages in the Kafka are stored in a log data structure in segment files and the way the message is stored has version limitations, that property is called log file version, we are using Kafka v2.7 across the cluster. The same versioning is applicable for message format version. Both of these configs work together to determine the performance of the overall Kafka cluster. Now using a lower version of the client will force us to reduce these configs values as well which in turn will reduce cluster performance for all users.
Do not place IBM confidential, company confidential, or personal information into any field.