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.