Fixed issues

This section lists the issues that have been fixed since the previous version.

CDPDSS-81: Data Catalog Issue
Problem:If an error occurs while fetching results, an error message appears briefly and disappears. Once the message disappears, the results pane is stuck in the Loading state.
CDPDSS-81: Data Catalog Issue
Problem: Despite having no privileges to add, modify, or delete classifications, users are able to edit the tag flow on the Asset Details page. However, users will not be able to save the changes.
CDPDSS-81: Data Catalog Issue
Problem: On the Asset Details page, the Audit tab fails to load if the logged in user does not have Audit read privilege.
CDPDSS-363: The 403 error message seen in Data Catalog > Table / Audit tab
Problem: Error messaging needs to be improved for users accessing Table and Audit tab without sufficient Ranger role.
CDPDSS-437: Unauthorized message for tag management flow does not have column name
Problem: Unauthorized column names and comma visible for tag management flow.
CDPDSS-444: Duplicate tag based policy on asset-360 Policy tab
Problem: When a specific tag is present both on the table as well as on any column of the same table, and a couple of requests to Ranger with the same tag and it displays the policy twice on list.
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.
CDPDSS-81: Data Catalog 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-517: Dataset View: Asset list displays loading icon if user is not authorized on Environment on which the dataset is created.
Problem: The dataset view page breaks if user does not have access to the Environment on which the dataset is created.
CDPDSS-570: The Filter type list should be refreshed based on the data lake selection.
Problem: Selecting the filter type from the drop-down does not display the supported entity type and also in the radio button list.
CDPDSS-547: Data lake name missing on the Asset-360 page.
Problem:The data lake name was not visible on the Asset-360 page .
CDPDSS-594: Database filter and create dataset button gets hidden
Problem:When you clear the query used the clear button, the databaser filter gets hidden and create dataset button on the search page gets disabled.
CDPDSS-636: User able to view assets of a dataset which is available in an inaccessible data lake.
Problem: Users are able to view the assets in a data lake for which they have no permission or access.
CDPDSS-672: On the Asset-360 page, when you make changes and save them, the Scheme page is refreshed, the Schema tab is disabled, and Overview tab becomes operational.
Problem:When you perform some operations on the Asset-360 page and save the changes, the Schema tab gets inactive.