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

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 (

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

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Not under consideration
Created by Guest
Created on May 20, 2019

IIDR Apply Engine for Kafka should pick up and inject via configuration.

See case number:  TS002220107 for details.

  • As detailed in the case is read from
  • The property injects into ConsumerConfig for all data channels.
  • The property does not inject into ProducerConfig for data channels.  Instead that value appears to be hard coded to value ""

Many Kafka Deploys use as a means for setting throttle quotas to plan and provision for capacity.  Dependent upon the policy of the deployed cluster the "default throughput" for producers with invalid can be throttled down to 1byte / sec.

In our scenario this is what we experienced.  This resulted in a timeout and subsequent "Failed to produce messages to commitstream" and fail of the subscription

Needed by Date May 31, 2019