IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Cloud Pak for Data
Created by Guest
Created on Sep 14, 2020

In-built CP4D Cloudera Impala connector should allow for custom JDBC parameters

When creating a connection and selecting the cloudera impala connector, the form used to configure the connection does not allow for JDBC parameters to be added at the end of the jdbc connection string,

e.g.

jdbc:impala://<HOST>:<PORT>/?<PARAM>=<VAL>&<PARAM2>=<VAL2>

This is needed due to the config of our Cloudera cluster using custom authentication settings.

Needed by Date Dec 31, 2020
  • Guest
    Sep 25, 2020

    With the exception of the Generic JDBC connector, we don't expose the details of the JDBC url and properties, this is because we reserve the right to swap out the JDBC driver implementation and not all drivers use the same url and properties. If a new auth method is needed, we could explore adding properties to the Cloudera Impala connector to support this, but we won't be adding the ability for the end user to manipulate the JDBC url or properties directly.