Cloudera Data Catalog on premises 1.5.5 SP3

What's new in Cloudera Data Catalog 1.5.5 SP3

This section lists major features and updates for the Cloudera Data Catalog service.

This release of Cloudera Data Catalog on Cloudera Data Services on premises 1.5.5 service pack 3 includes the following features and enhancements:

This section lists known issues found in this release of the Cloudera Data Catalog service.

CDPDSS-4491: Profiler launch fails after you assign the PowerUser role: If you log in with a user account that does not have the PowerUser role and you attempt to launch the Profiler, the operation fails as expected. After you assign the PowerUser role to the same user account and you attempt to launch the Profiler again without recreating the user, the launch fails with the following error:
Forbidden. User does not have permission to perform this operation.; Roles and rights details are cached for up to 10 minutes. After you assign the PowerUser role, wait up to 10 minutes, then launch the Profiler again.

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

CDPDSS-4438: Able to add conflicting Allow and Deny list rules at the same time.: Previously, Cloudera Data Catalog let you add or update Allow and Deny list rules so that conflicting rules could exist at the same time. This issue is now resolved.
CDPDSS-4442: Configuration showing incremental profiling as true even if passed as false in ODP: When running an On-Demand Profiler (ODP) on an iceberg table with incremental profiling set to false, the Job Summary page incorrectly displayed the setting as true (and vice versa) based on the global configuration set. This issue is now resolved. The profiler configuration logic is updated so that the per-job incremental profiling flag is now respected correctly in ODP job summaries.
CDPDSS-4657: Profiler pods are not running in air-gapped environment: Previously, in air-gapped environments, profiler pods could not progress past the initialization phase because container image pulls from the private registry failed with an authentication error. This issue is now resolved. An image pull secret is injected from PLS so profiler pods can authenticate image pulls from the private registry.