Skip to Main Content
Integration


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


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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.


Status Submitted
Categories Event Streams
Created by Guest
Created on Nov 10, 2025

Enhancement to IBM MQ Connector JSON record builder to include schema

Opening this idea for IBM MQ Connector to include record key/value schema for JSON payloads. This can either be created under new Record builder or maybe an enhancement to the existing JSON record builder. 

This will allow for the following:

  • Allow an option to provide schema as part of writing the record to Kafka with JsonConverter (key/value.converter.schemas.enable)
  • Allow the use of AVRO converters (ex. using either Apicurio Avro / Confluent Avro converters) which requires the Connect record to have an KeySchema / ValueSchema 
  • Allow validation of the JSON payload before writing the record to Kafka

Some ideas for the requirements:

  1. A way to configure the JSON schema by including an inline or file path config in the connector configuration.
  2. A configuration to enable JSON schema validation against the payload.
  3. Handle any invalid payload to be sent to DLQ if enabled.
Idea priority Medium