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 (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

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

IBM Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/


Status Future consideration
Created by Guest
Created on Feb 20, 2019

CDC Kafka KCOP to be able to subscribe any replication event

In current version of KCOP it is limited to subscribing to these replication event types:

ReplicationEventTypes.BEFORE_INSERT_EVENT,
ReplicationEventTypes.BEFORE_DELETE_EVENT,
ReplicationEventTypes.BEFORE_UPDATE_EVENT

KCOP should be allowed to subscribe to all replication event types so it take some action.  For example, suppose a table is truncated at the source, currently KCOP in the target is not aware of this fact.  KCOP may want to send a message into Kafka to allow consumers of the event stream to be aware of the truncation and thus be able to decide whether to ignore it or take some specific action to cope with it.     The main benefit of allowing the KCOP to subscribe to all replication events is to give it visibility on what is happening and allow it to decide what to do.    Not having this capability leaves KCOP blind.   Events such as truncation of tables can be common events in source systems (especially during batch processing) so allowing KCOP visibility of this event will be of wide use to many.