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 Employees should enter Ideas at https://ideas.ibm.com


Status Submitted
Workspace StreamSets
Created by Guest
Created on Dec 19, 2024

Have the ability to store the error records from and HTTP stage or JDBC stage seperately.

This feature request is to have the ability to write the erroneous records from an http stage (client/processor) or jdbc stages directly to a dedicated data source(local fs/table). Currently the failed records along with logs from all stages are written to a common data source selected. It will be challenging to read this log and isolate the errors related to a particular stage. If we have a dedicated data source for stages like http (client/processor) or jdbc, we can directly use this for data governance and recon tasks.

Example:

when an HTTP stage encounters an internal error, like HTTP_00: Cannot parse record, where the status code will be 200, the record will get dropped. In this use case, the ask is to have a mechanism to capture these records to a staging table dedicated to this stage separately (This table will contain errors only for this stage). This will reduce the overhead of having to go through the pipeline error record stream and isolating specific records.

Needed By Not sure -- Just thought it was cool