Cloudera Docs

Known Issues in Apache Atlas

Learn about the known issues in Atlas, the impact or changes to the functionality, and the workaround.

Known Issues in Cloudera Runtime 7.3.1

CDPD-67112: Import transforms do not work as expected when replacing a string which already has ":"
The character “:” is not supported in path replacements. The import succeeds but location remains unchanged. The character “:” must be avoided.
None
CDPD-69150: Unable to add labels or user defined properties in Japanese
Adding Japanese labels or user defined properties results in the error message: “Invalid label: データ, label should contain alphanumeric characters, _ or -”
None
CDPD-69279: Quick search does not return entities when using Japanese or Chinese characters to search properties
Entities, such as hdfs_path, are not returned by the search when their indexable properties are searched using partial search terms made of Japanese or Chinese characters. Only exact matches return results when searching the indexed properties made of Japanese or Chinese characters.
None
CDPD-68191: Suggestions do not return the correct results when searching multiple Chinese characters
Free text search does not return results when searching Chinese phrases made of multiple characters. Partial searches return the correct results.
None.
CDPD-71219: Regression : Suggestions don't work for single character words on indexable attributes
When searching for entities whose name (entity names are indexable) is a single character, search results are returned but suggestions are not. When searching for entities whose description (entity descriptions are not indexable) is a single character, both search results and suggestions are returned.
None.
CDPD-67450: Table name renaming operation is not updating or creating iceberg_table entity
Renaming an Iceberg table does not update the corresponding Atlas entity.
None.
CDPD-67089: Export/Import: When a table with Ozone path is exported as "connected", only the Ozone key is exported.
When table with Ozone path is exported as "connected", only Ozone key is exported. Other Ozone entities, such as Ozone volume, Ozone bucket are not exported.
None.
CDPD-43772: Performance issues with Atlas service
If there are lot of update operations and the compression type of column families of atlas_janus table is SNAPPY, then the Kafka message processing might become slower.
  • Consider setting compression type of column families of atlas_janus table as GZ.
CDPD-70450: Impala SQL queries that include the “WITH” clause should populate lineage in Atlas
Impala SQL queries that do not use the WITH clause can show lineage in Atlas, but queries that do use the WITH clause cannot show lineage in Apache Atlas. Impala SQL queries using the WITH clause are not supported.
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.file is 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.
CDPD-66938: [Analyze] [Atlas] [FIPS] 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.
Use explicit date range filters instead of using relative date range filters, such as, TODAY, YESTERDAY.
CDPD-70321: Atlas Parallel import is failing with various errors
During a parallel import-export activity with six iceberg table policies with exportOption as db1.* for all six exports, all import fail after the exports.
CDPD-76269: POST Rolling Upgrade performed from 7.1.7.3000 to 7.3.1.0 , and then downgraded from 7.3.1.0 to 7.1.7.3000 , updating edge to enable tag propagation is failing
When performing a rolling upgrade from 7.1.7.3000 to 7.3.1.0, and then downgrading from 7.3.1.0 to 7.1.7.3000, updating edge to enable tag propagation fails.
Tag propagation works well after a restart.
CDPD-76536: Iceberg entities created in 7.2.17 Atlas-Hook (Hive, Impala, Spark) are not ingested by 7.2.18/7.3.1 Atlas Server
Cloudera Data Warehouse version 2024.0.18.2-4 has the Cloudera Data Hub version 7.2.17 which supports an older Iceberg model for the Atlas hook. Apache Atlas in 7.3.1 data lake already supports the latest Iceberg model causing incompatibilities.
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-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-77767: Migration status is not updated on file while migration is in progress
Whenever a migration starts on any environment and the vertex is attempted to be updated with details, the status update fails with a null pointer exception.
None.
CDPD-71411: Atlas Hbase import fails with jackson-databind expection
The jackson-annotations is not updated to match jackson-databind (2.15.0). This causes the NoSuchFieldError error intermittently during an HBase import because of a version mismatch (older 2.12.7 on classpath).
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.
CDPD-80922: 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-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