Known issues

CDPDSS-2707: Custom Sensitivity Profiler (CSP) regex logic fails intermittently for complex regex

CSP regex logic fails intermittently for complex regex. Due to this intermittently the Cap tags do not get attached to Hive columns on execution of sensitivity profilers.

None

CDPDSS-2706: Data Steward user role is not reflecting

Data Steward role is not reflecting in Control Plane.

None

CDPDSS-2843: While upgrading to Data Services 1.5.3, an unnamed module @0x4e38d975 exception error is thrown

You must restart your Data Catalog Pod.

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-3077:

Datasets containing deleted assets fail to render the assets list with the following error: pages.dataset.labels.err-undefined-msg(Error Code - undefined)

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-2830: Data Catalog running on JDK-17 in PvC causes ClassNotFoundException and further failures

Cloudera Data Catalog running on JDK-17 in PvC causes ClassNotFoundException and further failures which leads to the service not coming up with a Bad Gateways error and being unusable. The following is logged in the Data Catalog pod:

----
INFO from c.g.i.Guice in [main] - - An exception was caught and reported. Message: java.lang.reflect.InaccessibleObjectException: Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @7a799159 - java.lang.IllegalStateException: Unable to load cache item
----

Use the environment variable in the deployment in the container specification:

----
name: JDK_JAVA_OPTIONS
value: --add-opens java.base/java.lang=ALL-UNNAMED --illegal-access=warn
----