Known issues and limitations for Data Product Hub

Data visualizations may fail for data products with many items

Applies to: 5.0.2 and later

In the minority scenario of a user creating a data product with many data items, Data Product Hub tries to create data visualization assets for all of the items simultaneously. In some rare instances, the creation of a visualization may fail for an individual item. If this occurs, the data product consumer cannot view the visualization.

The workaround is for the data product producer to return to the data product and click the item detail again in order to recreate the visualization.

Virtualized assets cannot be added to a data product

Applies to: 5.0.0 to 5.0.2

Fixed in: 5.0.3

Virtualized assets from a catalog cannot be added to a data product. An HTTP 400 Bad Request error may be generated when attempting to add a virtualized asset as an item in a data product.

Vaulted connections are not supported

Applies to: 5.0.0 and later

Data Product Hub does not support connections where the credentials are stored in a secret in a vault.

Failed delivery of data products when making CAMS REST API calls using Zen Token

Applies to: 5.0.0 to 5.0.2

Fixed in: 5.0.3

Data product delivery may fail if your environment includes making CAMS REST API calls via Zen Token which is generated through the Internal Service Token API. This can trigger an IBM Knowledge Catalog known issue related to cache corruption. If this occurs, the administrator must restart the CAMS pods. After the restart, the data producer must recreate the impacted data product.

Data protection rules are not enforced in data products

Applies to: 5.0.0 and later

Data protection rules such as redaction, obfuscation, and substitution are not enforced in a data product. When you add items that contain data protection rules to a data product, edit the data asset to ensure that no sensitive information is exposed.

Use the API to delete connections that are in use

Applies to: 5.0.0 and later

From the user interface, you cannot delete a connection that is in use by a published data product. Using the user interface, you must retire all the data products that use the connection before you can delete the connection. You can override the user interface by using the API. Use the following API call to delete a connection that is in use by one or more published data products:

Call the DELETE Connection endpoint to delete connections. For example:

DELETE /v2/connections/{connection_id}

When a connection is deleted by using the API, the items in the data products that use the deleted connection cannot be delivered. If there are items in a data product that use other connections, those items will still be deliverable.

For details, see Delete connection.

Data assets can only be added by owners

Applies to: 5.0.0 to 5.0.2

Fixed in: 5.0.3

When you create a data product draft, you can only search and add data assets that you own. Filtering by owner is also unavailable.