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.
DataStage: Kafka Connector in Information Server 11.7 does not support the use of schema registry or Avro JSON serialisation/deserialisation. IIDR (CDC) for Kafka on the other hand, produces Avro JSON serialised records into topics as default. Using Avro and schema registry have advantages for high volume and near-real-time integration use cases. At present, those benefits cannot be realised using IIS 11.7 Kafka Connector. More importantly, it does not support the default behaviour of IIDR for Kafka. This disadvantages the solutions and DataStage against competing technologies such as Talend which offers much superior support for Apache Kafka.
On other main issue using Kafka Connector in IIS 11.7 to consume data produced by IIDR for Kafka is the inability of Kafka Connector to handling NULL records. For physical deletes in a source, IIDR produces a NULL record at which point the DataStage job aborts.
CDC for Kafka: On the IIDR (CDC) for Kafka side, there should be some flexibility for developer to select a output format and serialisation method without forcing down the Avro JSON path. For example, being able to produce string serialised or byte array serialised CSV records into topics. Avro JSON requires a schema registry and it is not a generic Kafka SerDes (Serializer/Deserialiser). Although IBM has provided some user exits (KCOP - Kafka Customer Operation Processors) as a way around to this and produce records without a schema registry, using KCOP adds a processing overhead, since the producer first generates the record in Avro and then converts back by the KCOP to the desired format. In addition, only one KCOP can be used in a subscription and developer need to write custom KCOPs to combine any two or more non-standard CDC functions.
Do not place IBM confidential, company confidential, or personal information into any field.