Known Issues in Cloudera Runtime 7.2.18.1101
You can review the list of reported known issues in Cloudera Runtime 7.2.18.1101.
- 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".
- CDPD-75994: Post DL regular upgrade (non ZDU) to 7.3.1, "Exception in getKafkaConsumer ,WakeupException: null" is seen
- After the data lake is upgraded to 7.3.1, sometimes Atlas Hook
does not function when Apache Atlas and Apache Kafka are started at the same time, thus Atlas
is unable to connect to Kafka while Kafka is still being set up. Atlas performs only three
attempts.
Restart the cluster, after the upgrade to trigger to reconnect to Apache Kafka. The Kafka consumer creation should be retried if the Kafka service is unavailable during Atlas startup.
- CDPD-76035: Resource lookup for Atlas service is failing
- Once the Atlas configuration snippet
atlas.authentication.method.fileis enabled and a classification is created, these do not synchronize correctly to the Type Category resource field setting of Apache Ranger. The newly created classification won't be able to be selected as the Type Name. - 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).
