Cloudera Docs

Known issues

Learn about the known issues in Cloudera Data Catalog, the impact or changes to the functionality, and the workaround.

CDPDSS-2706: Data Steward user role is not reflecting
Data Steward role is not reflecting in Control Plane.
None
CDPDSS-3051: Profiler Jobs are not in the sorted order
Profiler jobs are incorrectly ordered when the list cannot fit into a single page under Profiler > Jobs. The latest job is displayed in the last page.
CDPDSS-3047: The profiled data is not shown for Ranger Audit Profiler
The profiled data is not shown for Ranger Audit Profiler if the active NameNode is switched over to standby.
Switch the NameNode in standby to active state. For more information on restarting nodes, see Starting, Stopping, and Restarting Role Instances or Administrative commands.
CDPDSS-3057: Failed profiler job because of missing columns in log entries.
When the logs to be profiled by the Ranger Audit Profiler have missing columns, the profiling job fails. The ranger audit profiler pod log contains the following message:Ranger Audit Profiler failed: Failed to run Ranger Audit Profiler. Error: "['column1', ' column2', ...] not in index".

column1 , column2 show the missing column entries in the logs.

Each Ranger audit profiler job has 3 sub-jobs (identified by the same job ID prefix), any of which could fail because of the above reason. It is possible that one or even two sub-jobs pass till the above scenario is encountered.

None
CDPDSS-3353: Profiler Configuration page is giving error, if browser's preferred language is not UK English
The Profilers > Configs is may be incorrectly rendered if the web browser's preferred language is not set to en-gb.
CDPDSS-2913: Asset Details view does not provide details of the asset - exception
Entities without lineage information may display the get linage request failed Error from Atlas Not Found : Received 404..
CDPDSS-3472: Profiler jobs are showing up twice when two data lakes are present
Cloudera Data Catalog does not support more than one data lakes (or base clusters). Connecting two data lakes will result in all profiler jobs showing as duplicated in the Profilers page.
CDPDSS-3346: Profiler pods are stuck in init state
The CDP_ACCESS_KEY_ID and CDP_PRIVATE_KEY keys do not receive values when upgrading from Cloudera Data Catalog 1.5.2 to 1.5.4.
  1. Use the following command to restart the DSS App: kubectl rollout restart deployment/cdp-release-dssapp -n <namespace>
  2. Delete and relaunch the profilers after the upgrade.
CDPDSS-3381: The Ranger Audit Profiler is showing status as FINISHED/SUCCESS even though there is error with the profilers
The Ranger Audit Profiler shows the incorrect FINISHED/SUCCESS status when the NameNode is stopped.
None
CDPDSS-3348: Only Dataset owners should be allowed to delete their datasets
Datasets can be deleted by anyone who can access the Datasets page.
None
CDPDSS-3081: Datasets: Tenant Schema is getting passed as workload username while impersonating a user on ATLAS and Ranger API calls
While making API calls to Apache Atlas and Apache Ranger, there is a potential bug in code where a wrong value for workloadUserName is getting passed which causes the APIs to perform an auth check with a wrong parameter, causing unwanted issues.
None
CDPDSS-3080: Deleted Entities in Atlas cannot be removed from Datasets
Entities deleted in Apache Atlas cannot be removed from Cloudera Data Catalog datasets.
None
CDPDSS-3077: The Datasets Details page fails to load the list of assets
Datasets containing deleted assets can fail to render the assets list with the following error: pages.dataset.labels.err-undefined-msg(Error Code - undefined)
CDPDSS-3050: Username is not visible in Cloudera Data Catalog for the Local Administrator user
The username for local administrator users can be hidden instead of showing in the bottom left corner of the navigation sidebar.
CDPDSS-3049: Expanded graph is displayed on every page of the Schema tab
In the Asset Details page under the Schema tab, the bar graph of profiled assets might stay visible for a selected asset even when moving to the next page in the list.
CDPDSS-3048: Filtering based on Job status Finished is not working
The profiler job filter Finished is working correctly now, displaying the relevant jobs.
CDPDSS-3042: Edit classification is failing with guid undefined error
Trying to edit the classifications in the Asset Details screen can result in the "List properties for entity request failed Error from Atlas. Not Found : Received 404. Body {\"errorCode\":\"ATLAS-404-00-005\",\"errorMessage\":\"Given instance guid undefined is invalid/not found\"}" message.
CDPDSS-3037: Asset Details page does not highlight link for Datasets
The Asset Details now correctly highlights links to Datasets.
CDPDSS-3524: Profiler pod launch is failing with init error
During the profiler cluster setup, when all the services pods are being deployed, Cloudera Data Catalog attempts to complete the prerequisites to set up a service and request to create a machine user. If the UMS service has not come up properly at that time, the request fails, and does not create the machine user dp_profiler_user required for profiling.
  1. Go to Management Console > User Management > Users.
  2. Search the machine user dp_profiler_user. Continue with the following steps, if the machine user is missing.
  3. Use the following command to restart Cloudera Data Catalog: kubectl rollout restart deployment/cdp-release-dssapp -n <***NAMESPACE***>.
  4. Delete and relaunch the profilers.
CDPDSS-3395: Incorrect results are being displayed after navigation, when "owners" filter is selected
In the Search page, when returning to the list of results after opening the Asset Details of one the results and repeating the search with the same filter, other entities belonging to owners different than the selected can appear.
CDPDSS-2688: Hive Column On-demand Profiler is failing but the Asset Details page is not updated with 'Failed State'
A failed Hive Column On-Demand Profiler job is incorrectly not updated to Failed state in Asset Details > Profilers.
CDPDSS-3509: Only power users should only be able to launch profiler and ODP profilers
When updating the roles of a user with the role poweruser to environment user, the user is still able to start on-demand profiling jobs. Starting on-demand profiling jobs should only be available for power users, not to environment users.