Known Issues in Cloudera Runtime 7.2.17.600

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

CDPD-82058: 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.
Apache JIRA: ATLAS-5015
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.
Avoid creating classification with reserved names such as "name", "description", "owner", "version", "serviceType" and "options".
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.

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.
It is recommended to upgrade your Atlas server version to at least 7.2.18 or later.