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:

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:

Workspace Cloud Pak for Data
Components Db2 Big SQL
Created by Guest
Created on Mar 5, 2021

Ability to create BigSQL table from a single environment (i.e. QA) against parquet files stored in two different Cloud Object Storage (i.e. QA and PROD)

We create a number of simulated test data in our QA environment COS with BigSQL tables and Data Virtualization. Before upgrading from CP4D 3.0 to CP4D 3.5, we ran some simulated test BigSQL queries in our QA environment.

Now that our QA has been upgraded to CP4D 3.5 and our PROD remains at CP4D 3.0, we would like to have the ability to create BigSQL tables in PROD with CP4D 3.0 and point the BigSQL tables to COS in QA. In doing so, we hope to be able to identify any potential BigSQL performance related question in CP4D 3.5 vs CP4D 3.0 using the "SAME" COS in QA.

Without this ability, we have to copy tera bytes of data from our QA COS to PROD COS. This request comes from TS004689570, which itself comes from TS004342312.

Needed by Date Mar 5, 2021