Skip to Main Content
IBM Cloud - Structured Ideas

This portal is to open public enhancement requests against IBM Cloud and its 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 (

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

IBM Cloud Support Center ( – Use this site for any IBM Cloud defect or support need.

Stack Overflow ( – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud". - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Oct 16, 2017

Allow users to set much larger retention times on topics to support more use cases, including kappa architectures

Some use cases are not possible with Message Hub because the topic retention times are too small.  One example is kappa architecture where you would like to reprocess your data after changing your stream processing logic.

  • Guest
    Feb 6, 2018

    This would have been useful with a recent RFP

  • Guest
    Oct 16, 2017

    Some more information on my use case ...

    I would like to load changes in reference data for a customer’s product data into kafka.  I’m currently loading the purchase transactions and would like to join the product data to the transactions to enrich the transaction data.  The product data is going to be in the region of MB rather than GB.  However, because I can only keep 30 days of state for the product data in the normal topics, because this data changes slowly, it would eventually all be deleted.  Therefore, I would need to (a) either rely on the ktable internal topic to save my product data, or (b) save the state in a db and somehow synchronise that with my streams app.  IMHO, neither of these options are any good.