Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 Employees should enter Ideas at https://ideas.ibm.com



ADD A NEW IDEA

Search results

Showing 17

Shutdown gracefully of IKC

Background: - Customer needs to restart the CP4D cluster to do maintenance operations as explained in : https://ideas.ibm.com/ideas/CPDIDEAS-I-2164 - The only service left with the "shutdown" feature for my customer is IKC. - Also, it will help us...
over 1 year ago in Cloud Pak for Data / Watson Knowledge Catalog 0 Under review

Enable rolling restarts of SDC as a standard pattern.

Currently, there are too many restarts of the SDC and all the SDC's dependent on the change in the deployment need to be restarted. Lets enable the restats to happen in a rolling manner, one SDC at a time. This capability is kind of available in a...
10 months ago in StreamSets 0 Under review

Enable self-service deployment of new JARs, JKS and custom libraries without requiring NFS or S3 buckets and without requiring SDC restarts

Very often users want to add new jars or have their own java key stores. Currently, these are done administratively and that too requires an S3 or NFS location and then requires a restart of the data collector. This involves engaging the administr...
10 months ago in StreamSets 0 Under review

QRadar: Maintain Last Position in Cisco FMC Log Collection via eStreamer Protocol

Description: When collecting logs from Cisco Firepower Management Center (FMC) using the eStreamer protocol, an issue arises if the FMC system undergoes a reboot. During the FMC reboot, traffic logs generated on Cisco Firewalls are sent after the ...
about 1 year ago in Connectivity 0 Under review

Port config issue on deployment

We have been facing issues with pods during restart of services and found this is related to a bug gap in the REST API used for deploying new pods and the port range assigned. Please reference case TS012155811 for more details.
over 2 years ago in Spectrum Conductor / Version 2.5.1 0 Under review

Support retries at the node level in Watsonx Pipelines

Currently Watsonx Pipelines do not support interacting at the node level for restarting tasks in case of failures and require rerunning the entire pipeline job. This makes it complicated to use for complex pipelines where any given task could fail...
over 1 year ago in watsonx.ai 0 Under review

Big Query connector uses legacy API by default which is adding 90 minutes of wait time for the streaming buffer to be flushed for DML operations to be performed. We need functionality in BQ connector to be able to use Storage write API to avoid this wait time

If a BQ job abends for some reason due to connectivity issue etc, the application team has to wait for 90 min to restart the job 2nd time. if this issue occurs in critical flow, it is causing SLA miss which is causing business impact
over 1 year ago in Connectivity 1 Under review