Known Issues in 7.1.7 SP3 CHF 8

Known Issues

KT-7591: KTS clusters result in installation failure in 7.1.7 SP3 CHFx

Fresh installation of KTS is not supported in 7.1.7 SP3 CHF8 as end-of-life of 7.1.7 is in August 2025.

You should be migrating to Ranger KMS.

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.

None

Apache Jira: ATLAS-4863

CDPD-80924: 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-66938: [Analyze] [Atlas] test_time_range tests fail

When the Apache Atlas server is running on a node which has time zone other than UTC, there might be a time of day when the search results might differ if the relative CreateTime date range filters of TODAY, YESTERDAY, etc. are used. For instance, if the server is in a different time zone from the user, TODAY may refer to different times than expected, causing mismatched results.

Use explicit date range filters instead of using relative date range filters, such as, TODAY, YESTERDAY.

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.

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".

Apache Jira: ATLAS-5067

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).

Start Atlas instances in sequence and not in parallel to avoid the potential race condition. If the exception is already present, restart the second Atlas instance after triggering the PermanentLockingException.