Known Issues in Apache Atlas

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

Known Issues identified in Cloudera Runtime 7.3.1.400 SP2

CDPD-83455: Basic Search API responding with unexpected values in response JSON: 7.3.1.400; The /v2/search/basic API endpoints can returns an unexpected result when Cloudera Data Catalog sends a search request with the equals keyword. Apache Atlas does not support the equals keyword and replies it; Only use the supported keywords when querying the /v2/search/basic endpoint:

=

!=

contains

begin_with

ends_with

is_null

not_null

Known Issues identified in Cloudera Runtime 7.3.1.300 SP1 CHF 1

The following section lists the known issues identified in this release:

CDPD-77434: When complete qualifiedName is provided as prefixString, sometimes search suggestions do not return the right suggestion: 7.2.18 and its service packs, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400; When searching for a newly created Iceberg table with the complete qualifiedName of an iceberg_column, the quick search does not list the Iceberg table as a suggestion sometimes.; None

Known Issues identified in Cloudera Runtime 7.3.1.200 SP1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.100 CHF 1

The following section lists the known issues identified in this release:

CDPD-77738: Atlas hook authorization issue causing HiveCreateSysDb timeout: Cloudera Runtime 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400; Atlas hook authorization error causes HiveCreateSysDb command to time out due to repeated retries.; None
CDPD-81092: Classic UI: Tables tab view stuck on loader in entity detail page: 7.3.1.300, 7.3.2; Cloudera Runtime 7.3.1.100, 7.3.1.200; When navigating to the Tables tab in the details of an entity, the Tables tab might get stuck during loading.; None
CDPD-81499: Basic search is lagging as some Datatypes not getting indexed in Solr: 7.2.18 and its service packsCloudera Runtime 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400; The Boolean datatype in Solr 3.6.2 is not indexed. When a search includes Boolean datatype, in-memory searching must be used. A larger dataset results in longer search time.; None
CDPD-82054: UI: when server response date fields as '0', UI shows as current time: 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300; 7.3.1.400; 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; None
CDPD-84502: Advanced Search is not working properly in Atlas UI: 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400; The Advance Search in Atlas does not return any results when selecting the Typedef option. The API is not triggered for each relation.; None.

Known Issues in Cloudera Runtime 7.3.1

CDPD-67112: Import transforms do not work as expected when replacing a string which already has ":"

7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

The character “:” is not supported in path replacements. The import succeeds but location remains unchanged. The character “:” must be avoided.

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.

7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

None.

CDPD-67089: Export/Import: When a table with Ozone path is exported as "connected", only the Ozone key is exported.

7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

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

7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

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-59413: Plugin is not supported with older Atlas server versions for Iceberg tables

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

Copy the model file 1130-iceberg_table_model.json to the directory: /opt/cloudera/parcels/CDH/lib/atlas/models/1000-Hadoop.

Proceed to restart the Atlas Service using Cloudera Manager.

CDPD-56590: Create table "like" from Iceberg table creates a hive_table instead of iceberg_table

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

By default, for tables created using the "like" command, lineage is not generated in Atlas. The destination like table should be of the same type as source table. Instead an iceberg_table for source and hive_table for destination are getting created.

CDPD-56085: [Impala Iceberg] LOAD DATA INPATH to Iceberg_table creates a temporary hive_table with name <iceberg_table_name>_tmp* and then marks it as DELETED in Atlas

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

Running a query like "LOAD DATA INPATH to iceberg_table", creates a temporary hive_table with name <iceberg_table_name>_tmp* and then marks it as DELETED in Atlas. So in Atlas, a deleted entity is created corresponding to the temporary table "<iceberg_table_name>_tmp*".

Tag added to the File system (HDFS) entity will not be propagated to the Iceberg table, user has to manually add to the iceberg_table, since the tag propagation is broken due to the deleted table in the flow.

CDPD-65806: After upgrading from Cloudera Runtime 7.2.17 to 7.2.18, not all Iceberg table relationships are visible in the entity details page

7.3.1, 7.3.1.100

7.3.1.200

None

CDPD-62973: Change in audits behavior in Cloudera Runtime 7.2.18 deployment.

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

When the value of differential audits is set as true, the audit information is not segregated based on the user which is firing the query. The HMS service user information includes details of the service user. When differential audit is enabled, only the difference between the two subsequent audits is logged, but in this case, there is no change in the data which is retrieved from HS2 and HMS, which does not create the audit. The user information is audited fine when differential audit is disabled

CDPD-55301: The ddlQueries and ALTERTABLE_* lineage are missing for Spark tables created using spark3-shell

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

The ddlQueries and outputFromProcesses (lineage) is missing for the alter queries.

CDPD-40346: The ddlQueries and ALTERTABLE_ADDCOLS lineage missing for Impala tables

The ALTERTABLE_ADDCOLS lineage has some issue when an Impala table is altered and the corresponding lineage is not created.

CDPD-55671: When one Atlas server host is not reachable (stopped), the GET request does multiple failover for approximately 4 minutes and takes around 2 minutes for every failover and finally the request fails.

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

None

CDPD-55122: Any user with ssh access can view the downloaded results

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

None

CDPD-45642: When REST Notification server is down, messages from hooks are lost

7.2.16 and its service packs and hotfixes, 7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

None

CDPD-46940: REST notification need to be disabled when running import scripts

7.2.16 and its service packs and hotfixes, 7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

Since import scripts and REST notification server both use atlas.rest.address, do not enable the REST notification while running import scripts or set atlas.rest.address to point to the default safety valve value.

None

ATLAS-3921: Currently there is no migration path from AWS S3 version 1 to AWS S3 version 2

None

CDPD-11692: Navigator table creation time not converted to Atlas

7.2.16 and its service packs and hotfixes, 7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

In converting content from Navigator to Atlas, the create time for Hive tables is not moved to Atlas.

None

CDPD-7982: HBase bridge stops at HBase table with deleted column family

7.2.16 and its service packs and hotfixes, 7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

Bridge importing metadata from HBase fails when it encounters an HBase table for which a column family was previously dropped. The error indicates:

Metadata service API org.apache.atlas.AtlasClientV2$API_V2@58112bc4 failed with status 404 (Not Found) Response Body
({""errorCode"":""ATLAS-404-00-007"",""errorMessage"":""Invalid instance creation/updation parameters passed :
hbase_column_family.table: mandatory attribute value missing in type hbase_column_family""})

None

CDPD-6675: Irregular qualifiedName format for Azure storage

The qualifiedName for hdfs_path entities created from Azure blog locations (ABFS) doesn't have the clusterName appended to it as do hdfs_path entities in other location types.

None

CDPD-4762: Spark metadata order may affect lineage

Atlas may record unexpected lineage relationships when metadata collection from the Spark Atlas Connector occurs out of sequence from metadata collection from HMS. For example, if an ALTER TABLE operation in Spark changing a table name and is reported to Atlas before HMS has processed the change, Atlas may not show the correct lineage relationships to the altered table.

None

CDPD-4545: Searches for Qualified Names with "@" doesn't fetch the correct results

When searching Atlas qualifiedName values that include an "at" character (@), Atlas does not return the expected results or generate appropriate search suggestions.

Consider leaving out the portion of the search string that includes the @ sign, using the wildcard character * instead.

CDPD-3208: Table alias values are not found in search

When table names are changed, Atlas keeps the old name of the table in a list of aliases. These values are not included in the search index in this release, so after a table name is changed, searching on the old table name will not return the entity for the table.

None

CDPD-3160: Hive lineage missing for INSERT OVERWRITE queries

Lineage is not generated for Hive INSERT OVERWRITE queries on partitioned tables. Lineage is generated as expected for CTAS queries from partitioned tables.

None

CDPD-3125: Logging out of Atlas does not manage the external authentication

At this time, Atlas does not communicate a log-out event with the external authentication management, Apache Knox. When you log out of Atlas, you can still open the instance of Atlas from the same web browser without re-authentication.

To prevent access to Atlas after logging out, close all browser windows and exit the browser.

CDPD-1892: Ranking of top results in free-text search not intuitive

The Free-text search feature ranks results based on which attributes match the search criteria. The attribute ranking is evolving and therefore the choice of top results may not be intuitive in this release.

If you don't find what you need in the top 5 results, use the full results or refine the search.

CDPD-1884: Free text search in Atlas is case sensitive

The free text search bar in the top of the screen allows you to search across entity types and through all text attributes for all entities. The search shows the top 5 results that match the search terms at any place in the text (*term* logic). It also shows suggestions that match the search terms that begin with the term (term* logic). However, in this release, the search results are case-sensitive.

If you don't see the results you expect, repeat the search changing the case of the search terms.

CDPD-1823: Queries with ? wildcard return unexpected results

DSL queries in Advanced Search return incorrect results when the query text includes a question mark (?) wildcard character. This problem occurs in environments where trusted proxy for Knox is enabled, which is always the case for Cloudera.

None

CDPD-1664: Guest users are redirected incorrectly

Authenticated users logging in to Atlas are redirected to the Cloudera Knox-based login page. However, if a guest user (without Atlas privileges) attempts to log in to Atlas, the user is redirected instead to the Atlas login page.

To avoid this problem, open the Atlas Dashboard in a private or incognito browser window.

CDPD-922: IsUnique relationship attribute not honored

The Atlas model includes the ability to ensure that an attribute can be set to a specific value in only one relationship entity across the cluster metadata. For example, if you wanted to add metadata tags to relationships that you wanted to make sure were unique in the system, you could design the relationship attribute with the property "IsUnique" equal true. However, in this release, the IsUnique attribute is not enforced.

None

CDPD-65619: Newly created Iceberg tables do not show up under hive_db entity

7.2.18 and its service packs and hotfixes, 7.3.1

7.3.1.100

When creating hive_table as well as iceberg_table, only the tables with the hive_table typename are shown under the Tables tab. Both Iceberg and Hive tables cannot be shown when they are created in the same hive_db entity.

CDPD-77257: When a HIVE CTAS Iceberg table is created, an extra "staging" HDFS path created is also in Apache Atlas

7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

When a Hive CTAS Iceberg table is created, there is an extra "staging" HDFS path created in Atlas for a directory, which would not be required.

None

CDPD-75994: Post DL regular upgrade (non ZDU) to 7.3.1, "Exception in getKafkaConsumer ,WakeupException: null" is seen

7.2.16 and its service packs and hotfixes, 7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

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

7.2.18.600, 7.2.18.700, 7.2.18.800, 7.2.18.900, 7.2.18.1000, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

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] test_time_range tests fail

7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

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

7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400

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

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1

7.3.1.100

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

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100

7.3.1.200

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

7.2.17 and its service packs and hotfixes, 7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100

7.3.1.200

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

7.3.1

7.3.1.100

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

7.3.1

7.3.1.100

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-80922: Without permission for one glossary, /glossary call throws exception

7.2.18 and its service packs and hotfixes, 7.3.1, 7.3.1.100, 7.3.1.200

7.3.1.300

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: NPE while deleting BusinessMetadata

7.2.18 and its service packs and hotfixes, 7.3.1

7.3.1.100

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

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.

CDPD-87670: [Atlas UI] Apache Atlas Glossary becomes unresponsive when the page size is set to 50

7.2.18 and its service packs and hotfixes, 7.3.1 and its service packs and hotfixes

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