Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Created by Guest
Created on Sep 11, 2019

Configure the "namespace" and "name" attributes generated by the CDC replication engine for Kafka

Description of the issue: We want to generate Java classes from the schema registry subjects associated to target topics in order to deserialize the keys and values of Avro messages written to this topics by the CDC replication engine for Kafka of Infosphere Data Replication. There are standard tools that generate the classes from the Avro record stored in the schema registry under a specific subject version (subject = topic-key or topic-value). These tools use the "namespace" and "name" attributes of the record as package name and class name respectively. The "namespace" and "name" attributes generated by the CDC replication engine for Kafka do not suite our needs for the following reasons:

  1. The "namespace"/"name" do not conform to our organizational naming conventions for Java classes.
  2. The "namespace" contains references to the environment at several places and is therefore not usable generically in our Java code.

We tried the following obvious workaround: read the records from the schema registry, modify the name und namespace in a new avro schema file and generate the classes from the new files. That unfortunately did not work (apparently the package and class names are matched against the namespace and name attributes at some point) and the messages could not be deserialized. Please let us know if you arrive to a different conclusion here.

IBM Workaround: The workaround supplied  did work, as far as we could tell. However, we would like a solution that is both officially supported by IBM and is directly integrated to the distribution. If possible, for basic functionality, we would like to avoid having to write and maintain our own KCOPs and rely instead on a solution provided and supported by IBM.

Needed by Date Dec 31, 2019