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 Future consideration
Workspace StreamSets
Created by Guest
Created on Sep 10, 2024

Improve Orchestrator Connection functionality for Control Hub REST API Processor

In SDC 5.12.0, there is a new Connection Orchestrator Connection which is available in all Orchestrator stages such as the Start Jobs stages.

ControlHub Rest API Processor also supports this connection.

The issue is that ControlHub Rest API stage doesn't have separate field to give Rest API Path when the Orchestrator Connection is selected.

  • So if we were to use this Orchestrator Connection, we'd need to mention full REST API URL including BaseURL/ControlHubURL + API Path in Connection's Control Hub URL field
  • Even if we create different orchestrator connection to call SCH REST API, then we will need multiple connections for same user to call APIs having different path.
    • We created separate connection for REST API by specifying Control Hub URL as ${str:concat("https://OurControlHubUrl.com:443", controlhub_api_path)}, where user will have to define pipeline parameter controlhub_api_path
    • Issue with that approach was when pipeline had multiple SCH Rest API Processors, they couldn't use same connection in all those stages.

We'd like a new feature where we have separate field in the ControlHub  Rest API processor to mention Rest API Path (excluding base URL) when an Orchestrator Connection is used.

Needed By Quarter
  • Guest
    Reply
    |
    Sep 17, 2024

    [heart] Hirave, Mayura reacted to your message: