Skip to Main Content
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:

Status Not under consideration
Created by Guest
Created on Jun 13, 2019

IA Semi-Structured Data Support

Currently, when ingesting Hive table metadata into Information Server using Metadata Asset Manager, if the Hive tables have complex data types that contain embedded data structures, such as an array of structs, the complex data is imported as a single STRING attribute instead of the complex data type itself, such as an array with a struct that also has embedded attributes. This limited representation of Hive complex data types within Information Server has the following impact on our ability to gain value from the data lake data within Information Server –

For context, let’s take the Example entity, example_detls, which has the attribute Example Details History, which is a complex attribute that is an ARRAY of STRUCTS with the embedded attributes such as Example Code 1, EXAMPLE1_CD, and Example Code 2, EXAMPLE2_CD.

  1. Within Information Analyzer, we are not able to effectively bind data validation rules to the embedded struct elements, such as EXAMPLE1_CD, limiting our ability to perform data quality via Information Analyzer.
  2. Within Information Governance Catalog, we are not able to effectively search for the embedded elements, classification, see the lineage, or just casually drill down when visualizing the element.
  3. We are also not able to effectively perform data profiling on the embedded struct elements.


Another thing to note is that the presentation of the Native Type attribute in IGC, which does attempt to display the complex data type metadata as is, often truncates that metadata during presentation. This truncation makes the metadata of little use.

Needed by Date Sep 1, 2019
    Sep 28, 2020

    Thank you for your idea. All enhancements requests will be considered for IBM Watson Knowledge Catalog moving forward.