This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
The proposed idea is to create a native connector that can be instantiated like the other connectors in the palette and that is able to integrate the confluent schema registry to produce or consume an event on Kafka according to an avro schema, a json schema or protobuf.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Idea review. Thank you for taking the time to raise this suggestion, which we agree would improve the product. Whilst we have the ability to inspect Kafka properties which highlight the avro schema in use, it would be good to have the KafkaConsumer and KafkaProducer directly interact (download/upload) with the schema from the registry, and place it in to the environment tree ready for use in a downstream Java Compute node. This topic has already been raised under idea APPC-I-663 so to avoid the dilution of future voting, we are returning this idea as a duplicate and respectfully ask future readers to consider placing a comment and vote on to 663 (https://integration-development.ideas.ibm.com/ideas/APPC-I-663).