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 Submitted
Created by Guest
Created on Mar 16, 2022

Kafka Connector - Avro Schema name configuration

The current Kafka Connector ( SP1) does not allow us to configure Avro Schema name used for either serialization or deserialization.

In all cases, it is currently fixed to "KafkaConnectorSchema" which does not comply with our current schema name standard and triggers compatilibity errors when connecting to our Schema Registry.

We did not find any option to configure the Avro schema name used by the Kafka connector in order to solve this issue.

It would be great to add an option to setup a specific Avro schema name in order to allow compatibility with existing schemas. This current missing feature prevent us from using this connector for most of our integration needs between InfoSphere DataStage and Kafka.

Needed By Yesterday (Let's go already!)