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,
Post an idea
Upvote ideas that matter most to you
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.
Support of streaming/parsing/converting CLOB/BLOB type data structures in DV for larger data elements such as binary images that reside as objects on an S3
RequirementIntegrated GovernanceIn order to be able to use the CP4D Data Virtualization in combination with Watson Knowledge Catalog as a single, integrated governance layer over structured data (residing in Databases / Flat files) and unstructure...
DV Admin should be able to manage access of more than one "My Virtualized Data" at the same time. See TS004587996.
TS004587996 has all the details. The current UI design only allow one my virtualized data to be managed at a time. In order to manage access of one virtualized data, 7 to 10 clicks are required. With 70 virtualized data to manage, this quickly bec...
JOIN keys in JOIN stage should be able to be used even if each fields/columns have different names in each.
When users use Join stage for TableA and TableB, if each join keys have different column name (for example, each join key’s column names are col1a in Table A and col1b in Table B), it goes to error.
Our customer strongly requests us to improve so...
Ability to create custom role in Data Virtualization
At the moment, Data Virtualization (aka DV) comes with 4 pre-defined roles, i.e. https://www.ibm.com/support/knowledgecenter/en/SSQNUZ_3.5.0/svc-dv/dv_user_management.htmlAfter virtualize some table, if user wants to grant others access to the new...
Hi,According to an answer that we receive, the schemas name is only a suggestion and can be anything you would like when creating the Schema. By default, the Schemas are not owned by anyone, as a result, the other users can see all schema names bu...
Display the warning when User would delete DV table that used in the analytics projects be someone created.
When we would delete a DV(data virtualized) table, we want to the information where is one DV table used. Because, if someone is using this DV table, it is probrem that DV table be deleted.Current workaround is nothing.
Publish to any catalog from my virtualized data if there is more than one catalog in the system
At the moment, we will create a project, add the virtualized data to the project as data asset then publish data asset to catalog of our choice. It will be great if we can do this from data virtualization directly.
A tab-separated values (TSV) file format should be supported as source data in Data Virtualization.
A tab-separated values (TSV) file format should be supported as source data in Data Virtualization. (A Japanese Client) CSV file format is listed in the supported data source list for Data Virtualization as below.https://www.ibm.com/support/knowle...
All tables should be able on Data Virtualization with Strict mode
We need to assign business term to all column names and table name with Strict mode in Data Virtualization. Because if there are column name or table name that is not assigned business term, this table doesn't appear in DV. But we would like to as...
Do not place IBM confidential, company confidential, or personal information into any field.