Known issues

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

CDPDSS-2488: In MGMT service of DH CM, the telemetry command is failing bringing the master node down

When a Cloudera Data Hub cluster is created, the management service of Cloudera Manager becomes unavailable because the telemetry command fails on Hive. Because of this, the Master node of Cloudera Data Hub goes down causing a Node Failure error on the cluster.

In Cloudera Data Catalog, due to the failure of the master node of Cloudera Data Hub, the Profiler and the On-Demand Profiler page in the Asset Details page does not load.

It is recommended to upgrade to Cloudera Data Catalog 3.0.0 to avoid this issue.

CDPDSS-3364: Not able to delete the profilers from DSS App when underlying compute cluster deleted

When deleting the compute cluster in Compute Cluster enabled environments profilers cannot be deleted. The following error is displayed: Failed to delete profilers with error 401.

CDPDSS-3403: Altered ICEBERG table is not available in Compute Cluster enable environment

Iceberg tables modified or renamed with the ALTER operation appears with both old and new name, however, neither entry can be accessed. Apache Atlas synchronizes the table with the altered name with its full qualified name instead of its name shown in the Search results.

CDPDSS-3412: Profiling is not working on migrated ICEBERG table

Hive tables migrated to Iceberg with the ALTER TABLE statement cannot be profiled in Compute Cluster enabled environments. Cluster Sensitivity Profilers and Hive Column Profilers will not be able to apply tags to the values.

CDPDSS-3401: Profiler is shown as running in DSS App on deleting default compute cluster

In a Compute Cluster enabled environment, after deleting the default Compute Cluster profiler are displayed as still running in the Dashboard. However, profiler jobs will fail even if the default Compute Cluster is recreated.

After recreating the Compute Cluster, delete and relaunch the profilers.

CDPDSS-3323: Profiler Jobs are running forever if the primary Kubernetes pod is shut down

If the primary Kubernetes pod is forced shut down, or shuts down because of an error, the Kubernetes scheduler requests new resources for new pods. However, the original pod shut down still appears as a running job in Profiler / Jobs. This job cannot be deleted, as it is falsely marked running.

CDPDSS-3387: Profiling of struct or composite data type are not supported in Cloudera Data Catalog

Profiling of struct or composite data type are not supported in Cloudera Data Catalog. When profiling tables with such data. the profiling job will be stuck in the Undetermined status.

CDPDSS-3561: The number of columns is displayed incorrectly when the DB or table name is too long

In Asset Details, the number of columns (# of Columns) is displayed as zero when the database or table name is too long.

CDPDSS-3877: Unable to search for classifications while creating Apache Atlas tags

While creating a new Atlas tag for a tag rule for the Data Compliance Profiler in Create Tag Rule > Create New Tag, the Classification (optional) field does not offer the available classifications already present in Atlas for selection. Tag rules can be created regardless of this.

None

CDPDSS-3873: No validation for existing Tag Rules in Create/Edit Tag Rule flow

Cloudera Data Catalog does not check if the Tag Rule Name was already used for a previously created tag rule. Using the same tag rule name produces a HTTP 500 error.

Manually check if your new tag rule name was already used in Profiler > Data Compliance Profiler > Tag Rules.

CDPDSS-3862: Date range filter and pagination is not showing any results in Job History

Applying the Time Range filter when the second page is selected in Profilers > Profilers Details > Job History.

None

CDPDSS-3852: Number of Columns count is getting incremented on creating new tables

In Search > Asset Details, the # number of Columns value may not match the real number of columns in the table.

None

CDPDSS-3879: Removing the assets from Dry Run list takes two clicks

In Profilers > Data Compliance Profiler > Tag Rules > Dry Run Test the selected assets in Test Connection with Catalog Data can be removed from the field by clicking the icon twice.

None

CDPDSS-3880: Filter for associated tag does not return any data

In Profilers > Data Compliance Profiler > Tag Rules the Associated Tag filter does not show parent tags when selected.

None

CDPDSS-3870: Tag Rule Status is getting removed in the Edit Tag Rule wizard

In some cases when editing an existing tag rule, the Tag Rule Status settings gets hidden. However, this does not impact the status of the tag (enabled or disabled on the data lake).

None

CDPDSS-3865: Switching from Basic Schedule to Cron Expression results in error

Switching from the CRON based expression to the natural language based (Basic) schedule, not making any changes to the latter and moving back to the CRON based expression results in an error for missing fields but it does not affect known flows.

None