Known issues

This section lists known issues that you might run into while using the Data Catalog service.

CDPDSS-213: Launching of Profilers failing for older SDX instances
Problem: When you try to launch Profilers with older SDX instances, the launch operation fails.
Workaround: Make sure you launch Profilers for new SDX instances.
CDPDSS-144: Filter Results Count Mismatch
Problem: When you search and filter the results using Created Before, the count displayed in the filters panel is incorrect. But, the number of search results is accurate.
CDPDSS-144: Search icon within dataset does not work
Problem: When you try to search for an asset within a dataset and click the search icon, it does not yield any results.
Workaround: Press enter to view the search results after entering a string in the search box.
CDPDSS-143: Edit button appears after creating a new dataset
Problem:After creating a new dataset, when you visit the dataset, the Edit button appears instead of Add Assets.
Workaround:Refresh your browser and reopen the dataset. You will be able to see the Add Assets button.
CDPDSS-81: Data Catalog Known Issue
Problem: When you select a table tag, owner filters along with the counts disappear.
Workaround: Make sure you select table tags before selecting the owner filters.
CDPDSS-81: Data Catalog Known Issue
Problem: When you navigate to the Data Catalog page from the Environments page or Data Lakes page, the context is not retained and the Data Catalog page loads with the last used context.
Workaround: You must change the context manually by selecting the right data lake.
CDPDSS-302: Profiler Manager server requires a manual restart after installation for DP Tags to reflect in Atlas
Problem: Once the profiler is launched, run the sensitivity profiler, the profiler recognises the sensitive tags but fails to push them to Atlas.
Workaround: You must restart the profiler manager. Note that restarting the profiler manager is a one-time task.
CDPDSS-342: Deleted table is still shown in dataset
Problem: Created table in a dataset if deleted, does not get deleted completely and shows up in the dataset. If the same table is created again, the edit and search options are enabled. When you save the table, there are two tables displayed, thought the first instance of the same table was deleted.
CDPDSS-360: DP Profiler do not support managed Hive tables.
Problem: DP Profiler cannot access the storage file of the managed table.
CDPDSS-362: dpprofiler.submitter.batch.size property is not taking effect
Problem: As part of application.conf safety valve under profiler scheduler, applying the property dpprofiler.submitter.batch.size is not taking effect. It defaults to 50.
CDPDSS-412: Support for Data Catalog on 7.0.2 runtime SDX. In 7.0.2, Data Catalog profiler jars are not part of pre-warmed images of 7.0.2 runtime.
Workaround: Data Catalog users who are on 7.0.2 runtime SDX can launch profilers, provided explicit entitlement access is granted for the location of profiler jars.
CDPDSS-527: Data Catalog specific user roles not supported.
Problem: The following Data Catalog user roles are not supported:
  • DataCatalogCspRuleManager
  • DataCatalogCspRuleViewer

Adding or removing these roles in the User Management will not have any impact on Data Catalog user access.