Cloudera Docs

Cloudera Data Catalog on premises 1.5.5 SP4

Review the features, fixes, and known issues in the Cloudera Data Catalog 1.5.5 Service Pack 4 release.

What's new in Cloudera Data Catalog 1.5.5 SP4

New features and functional updates for Cloudera Data Catalog are introduced in Cloudera Data Services on premises 1.5.5 Service Pack 4.

This release of Cloudera Data Catalog on Cloudera Data Services on premises 1.5.5 service pack 4 includes the following features and enhancements:
  • Backup and restore support through the Data Recovery Service (DRS): You can now back up and restore Cloudera Data Catalog as part of a control-plane-wide backup and restore on Cloudera Embedded Container Service (ECS). This functionality is not available on OpenShift Container Platform (OCP). For more information, see Data Recovery Service overview.
  • Bug and CVE fixes

Known issues in Cloudera Data Catalog 1.5.5 SP4

Known issues for Cloudera Data Catalog are documented for Cloudera Data Services on premises 1.5.5 Service Pack 4 to identify unresolved behaviors and provide operational workarounds.

CDPDSS-4914: Profiler fails on secondary cluster after DRS restore
If a profiler was launched on the primary cluster while creating a backup, and a restore is performed on a secondary cluster, the profiler fails to work. This occurs because the cdp-pvc-truststore configmap in the dcprofiler namespace retains the certificate details of the primary cluster.
To resolve this issue, copy the cdp-pvc-truststore configmap from the cdp namespace to the dcprofiler namespace by running the following command: 
kubectl get configmap cdp-pvc-truststore -n cdp -o yaml \
  | sed '/resourceVersion:/d; /uid:/d; /creationTimestamp:/d; s/namespace: cdp/namespace: dcprofiler/' \
  | kubectl apply -f -
Alternatively, you can delete all profilers in the secondary cluster and set them up again to generate the correct configmap.
CDPDSS-4948: Search page returns a 500 error when an Atlas instance is down
In an environment where Atlas high availability (HA) is enabled, the Cloudera Data Catalog Search page is blank and returns an HTTP 500 internal server error if the Atlas instance that Cloudera Data Catalog connects to is not running. Cloudera Data Catalog connects to the first Atlas instance that is configured and does not redirect requests to the other instance.
None
CDPDSS-4949: Profilers do not run when an Atlas instance is down
In an environment where Atlas high availability (HA) is enabled, profiler jobs fail if the Atlas instance that the profiler connects to is not running. The profiler connects to the first Atlas instance that is configured and does not redirect requests to the other instance. The profiler log reports a connection error similar to the following:
Could not get table results from in atlas error :HTTPSConnectionPool(host='[***ATLAS-HOST***]', port=[***PORT***]):
Max retries exceeded with url: /api/atlas/v2/search/dsl?query=...
(Caused by NewConnectionError(... Failed to establish a new connection: [Errno 111] Connection refused))
None

Fixed issues in Cloudera Data Catalog 1.5.5 SP4

Fixed issues for Cloudera Data Catalog 1.5.5 Service Pack 4 provide resolutions for identified bugs or vulnerabilities.

There are no fixed issues to report in this release.