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.
Writeback to object storage and databases through data virtualization layer
Real-Life ScenarioIn our Data Lake, we want to expose all of our data sources (structured and unstructured) to our customers in an unified data virtualization layer.In one use case, we want to train an AI algorithm on the data and flag those files...
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...
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.
It should be chooseable OUTER of INNER JOIN in DV.
In DataVirtualization, we can create join view. But we can create only inner join view by using GUI. We know we can create outer join view by using SQL editor. But it is not acceptable from our customer.
Currently, We can't deployment multiple DV instance services. This may bring some limits, especially for sensitive data.Please consider adding support for this. Our scenario needs to support multiple departments/groups using DV, and the related da...
We are unable to join more than 2 views at a time in DV UI. If we have 4 views that need to be joined, we have to first join 1 and 2 together as view A, then 3 and 4 together as view B, then we can join those newly joined A and B views together.We...
There are multiple data source connection in DV for the same data source (HANA in this case) with different user authentication details. Connection names are not defined in the list of views that are pulled from data source connections and hence,...
Do not place IBM confidential, company confidential, or personal information into any field.