Known Issues in Cloudera Runtime 7.2.18.500
Learn about the known issues in Cloudera Runtime 7.2.18.500, the impact or changes to the functionality, and the workaround.
Known Issues
- CDPD-81958: Improve Cookie Security in Knox-Proxied Web UIs with Secure and HttpOnly Attributes
- The
pac4jCsrfToken
cookie has neitherHttpOnly
norSecure
flags in Knox proxied applications. This can lead to the cookie being sent over an unencrypted HTTP connection resulting in a security risk. - OPSAPS-69317: Kafka Connect Rolling Restart Check fails if SSL Client authentication is required
- The rolling restart action does not work in Kafka Connect when the ssl.client.auth option is set to required. The health check fails with a timeout which blocks restarting the subsequent Kafka Connect instances.
- CDPD-77399: HBase fails to register the servlet metrics and throws ClassNotFoundException: org.apache.hadoop.metrics.MetricsServlet
- The MetricsServlet class is a Hadoop 2-based metric servlet unavailable in Hadoop 3 deployments.
- TSB 2025-797: Using Spark vectorized reads on Iceberg tables with Parquet files could result in malformed data
- Due to an upstream Apache Iceberg issue, in specific situations, customers executing Spark vectorized reads on Iceberg tables with Parquet files may encounter malformed output and data incorrectness.
- CDPD-81554: Without permission for one glossary, /glossary call throws exception
- When you don't have the permission for a glossary, the
/glossary call results in a exception, blocking authorization for all glossaries. The
error message is the following:
{ "errorCode": "ATLAS-403-00-001", "errorMessage": "hrt_qa is not authorized to perform read entity: guid=*********-****-****-****-*******"}
- CDPD-67942: Atlas can't search Chinese/Japanese comment properly
- Entities whose comments contain Chinese or Japanese characters cannot be searched by using the comment (string), containing filters.
- CDPD-69910, CDPD-79161: NPE while deleting BusinessMetadata
- If business metadata is created without adding any applicable types, a NullPointerException is produced when trying to delete that business metadata.
- CDPD-82057: UI: when server response date fields as '0', UI shows as current time
- If an API response contains an invalid date value (such as 0) intended for display on the user interface, the current system date is shown. This issue specifically affects the Entity Detail page, where the create time and modified time are displayed.
- CDPD-76789: Creating tag with name description throws java.lang.ClassCastException
- Creating classification with reserved names such as "name", "description", "owner", "version", "serviceType" and "options" can lead to HTTP 500 error in Apache Atlas.
- CDPD-77435: RAZ: Import-hive on Cloudera Data Engineering cluster fails
-
Running import-hive command on RAZ enabled Cloudera Data Engineering cluster fails with error "NoClassDefFoundError: com/sun/jersey/core/spi/factory/ResponseBuilderImpl".
- DOCS-26821: Iceberg entities created in 7.2.17 Atlas-Hook (Hive,Impala,Spark) is not ingested by 7.2.18/7.3.1 Atlas Server
- When using an Atlas hook from 7.2.18 or later version (7.3.1) with an earlier version of Atlas server (7.2.17 or earlier) to create an Iceberg table, the older data model of Iceberg cannot process the features of the new data models. For example, when encountering relationships or attributes in queries which do not have a definition in the earlier model, Iceberg fails to create new tables with an error message. The data model of the Iceberg in Cloudera Runtime 7.2.18 or later is not backward compatible with earlier data models.
- CDPD-87670: [Atlas UI] Apache Atlas Glossary becomes unresponsive when the page size is set to 50
- When the page limit is set to 50 in Glossary, the user interface becomes unresponsive due to an incorrect API call with the error message, when trying to show more than 25 associated entities for a glossary item: "expected type AtlasGlossaryCategory; found AtlasGlossaryTerm".
- CDPD-28741: Atlas node start failure : PermanentLockingException: Expected value mismatch for KeyColumn
- In an Atlas High Availability (HA) enabled environment, starting both Atlas hosts at the same time can result in both trying to access or modify the same graph database resulting in a race condition. One instance successfully modifies the patch vertex, while the other instance triggers a Locking Exception (Concurrent modification exception).