Known issues and limitations
The following known issues and limitations apply to Data Product Hub.
Known issues
Permission issue in the custom metadata admin UI
Data product administrators are unable to access custom metadata admin UI in Data Product Hub standalone.
Workaround: Assign manage_catalog
permission for users. This permission will be available with Administrator role.
Gateway timeout errors when requesting data views for watsonx.data assets.
When requesting data views for watsonx.data assets, you may frequently encounter gateway timeout errors. These requests often take longer to process causing them to exceed the gateway timeout threshold and be terminated. The time to complete data view requests can vary depending on the connection type.
Workaround: If a gateway timeout occurs before the visualization request completes, you can try reinitiating the data view using the Refresh Preview option.
Regional support
Data Product Hub is currently available in the US Dallas (us-south), Australia (Sydney) au-syd and Canada (Toronto) ca-tor regions. The region switcher lists other regions, but they are not supported at this time.
Visualization availability in the Sydney region
The visualization to preview the items in a data product is not available from the Australia (Sydney) - au-syd region.
Assign the Viewer role to the Data Product Hub Service ID (for early adopters)
If you provisioned Data Product Hub before May 2024, the IBM Cloud account administrator must explicitly assign the Data Product Hub > Viewer role to the Data Product Hub Service ID. This step is required only if the Data Product Hub service was provisioned before May 2024. The access policy is automatically assigned for Data Product Hub instances provisioned starting in May 2024.
Follow these steps to assign a role to the Service ID:
- As the account administrator or owner, open the Manage > Access(IAM) > Service IDs page for your IBM Cloud account.
- Search for the data-product-admin-service-id-xxxx Service ID and click it to open the Access page.
- If the Data Product Hub > Viewer role is not listed under Access policies, click Assign access.
- Choose the Data Product Hub Service and complete the steps to assign the Viewer role.
Limitations
Insights dashboard subscriptions chart not showing all subscriptions
In your Insights dashboard, the subscription line graph can display data for up to 200 subscriptions only.
Tasks tile does not show all tasks from task inbox when user has access to view Community insights
When a user has access to view Community Insights but does not have permission to view all tasks in the Task Inbox, the Tasks tile will only display statistics for tasks assigned to them (similar to My Insights), instead of showing statistics for all tasks from task inbox.
Data product providers can be assigned as domain owners
Community administrators and editors can be assigned as domain owners, regardless of their current permissions. However, if domain owners log in without the required permissions, then they won’t have elevated access to the domains.
FIPS enabled cluster in 5.2 is not supported for watsonx.data delivery method
Deliver as a table in watsonx.data delivery method does not support FIPS enabled cluster in 5.2
Cloud Object Storage is only supported for storage connection for watsonx.data delivery method
Deliver as a table in watsonx.data delivery method only supports Cloud Object Storage for storage connection.
Watsonx.data delivery methods require watsonx.data to be in the same region
To use the watsonx.data delivery methods, Data Product Hub and watsonx.data must be installed in the same region.
Use the API to delete connections that are in use
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.
Parent topic: Documentation for Data Product Hub