Cloudera Docs

Known Issues in Atlas

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

CDPD-6565: Issue with ddlQueries in Atlas for Hive/Impala tables created in default/non-default db using DAS/HUE respectively
ddlQueries are not created for Impala origin table. ddlQueries created for Impala/Hive CTAS tables have difference in names as compared to same operation for Hive table. The Impala table has the query in the ddlQueries entity name.
None
CDPD-55301: ddlQueries and ALTERTABLE_* lineage missing for Spark tables created through spark3-shell
The ddlQueries and ALTERTABLE_* lineage missing for Spark tables created using spark3-shell.
None
CDPD-56085: 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
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*.
None
CDPD-58581: storage_handler is not set in Atlas for Impala to Iceberg in-place migrated tables
The storage_handler property is not set for Iceberg tables created in Impala, because in-place migration is not supported in Impala for the current release.
None
CDPD-58554: Discard audits of specific classification, label, and business metadata
Support to control audits for specific classification, label, and business metadata is not present in the Custom Audit Filters feature.
None
CDPD-58412: Ranger KMS APIs returning incorrect HTTP response codes for error cases
In case keys are not found while doing any operation on that, KMS returns 500 internal server error. Instead, it should return proper error code.
Such calls execution does not bring KMS to any inconsistent state and further calls with correct key name will be processed normally.
OPSAPS-67783: During rolling upgrade one among two Atlas server failed to start but Cloudera Manager considered as success
Cloudera Manager marks the Execute command Start on service Atlas-1 as a success even when Atlas service had failed to start successfully. In such cases, Atlas logs give the exact reason for Atlas start-up failure.
None
CDPD-19358: "IsIndexable"and "isOptional" value of a typedef's attribute is modified post migration.
None.
CDPD-11941: Table creation events missed when multiple tables are created in the same Hive command
When multiple Hive tables are created in the same database in a single command, the Atlas audit log for the database may not capture all the table creation events. When there is a delay between creation commands, audits are created as expected.
None.
CDPD-11940: Database audit record misses table delete
When a hive_table entity is created, the Atlas audit list for the parent database includes an update audit. However, at this time, the database does not show an audit when the table is deleted.
None.
CDPD-11692: Navigator table creation time not converted to Atlas
In converting content from Navigator to Atlas, the create time for Hive tables is not moved to Atlas.
None
CDPD-11338: Cluster names with upper case letters may appear in lower case in some process names
Atlas records the cluster name as lower case in qualifiedNames for some process names. The result is that the cluster name may appear in lower case for some processes (insert overwrite table) while it appears in upper case for other queries (ctas) performed on the same cluster.
None.
CDPD-10574: Suggestion order doesn't match search weights
At this time, the order of search suggestions does not honor the search weight for attributes.
None.
CDPD-9095: Duplicate audits for renaming Hive tables
Renaming a Hive table results in duplicate ENTITY_UPDATE events in the corresponding Atlas entity audits, both for the table and for its columns.
None.
CDPD-7982: HBase bridge stops at HBase table with deleted column family
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-7781: TLS certificates not validated on Firefox
Atlas is not checking for valid TLS certificates when the UI is opened in FireFox browsers.
None.
CDPD-6675: Irregular qualifiedName format for Azure storage
The qualifiedName for hdfs_path entities created from Azure blog locations (ABFS) does not have the clusterName appended to it as do hdfs_path entities in other location types.
None.
CDPD-5933, CDPD-5931: Unexpected Search Results When Using Regular Expressions in Basic Searches on Classifications
When you include a regular expression or wildcard in the search criteria for a classification in Basic Search, the results may differ unexpectedly from when full classification names are included. For example, the Exclude sub-classifications option is respected when using a full classification name as the search criteria; when using part of the classification name and the wildcard (*) with Exclude sub-classifications turned off, entities marked with sub-classifications are not included in the results. Other instances of unexpected results include case-sensitivity.
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 the metadata collection from HMS. For example, if an ALTER TABLE operation in Spark that is changing a table name and is reporting 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 "@" does not 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, and use 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 does 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 logout 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 CDP.
None.
CDPD-1664: Guest users are redirected incorrectly
Authenticated users logging in to Atlas are redirected to the CDP 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: The 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, to add metadata tags to relationships that you wanted to make sure were unique in the system, you can design the relationship attribute with the property IsUnique equal true. However, in this release, the IsUnique attribute is not enforced.
None.
DOCS-13759: Tag Propagation stops after a certain depth while the lineage is being extended
When a tag is added to an entity at timestamp T1, the entities along the lineage to which the tag must be propagated is calculated at T1. Before tag propagation completes, if the lineage is extended, tag does not propagate to the entities in the extended lineage.
DOCS-13760: System Attributes search, __classificationNames: Search with parent tag does not return entities associated to its children tags
System attribute search with __classificationNames = parent_tag returns entities associated to parent_tag only and not entities associated to its children tag.
Instead of using system attribute, employ the basic search attribute classification which lists entities associated with inherited classifications.
CDPD-41142: When a Kafka console consumer group is run, more than one update audits are seen
After running the console consumer with a consumer group, verify the consumer group entity created, along with the metrics and notifications for the consumer group and topic. The expected result can be: one ENTITY_CREATE audit and one ENTITY_UPDATE audit. But more than one ENTITY_UPDATE audits are seen.
CDPD-40165: Two audits are created for SPARK CTAS table

When following Spark queries are fired:

spark.sql("create table table1(id int)")
spark.sql("create table table2 as select * from table1")

HMS sends "ENTITY_CREATE" and "ENTITY_FULL_UPDATE_V2".

The extra ENTITY_FULL_UPDATE_V2 message received from HMS is sent as a part of ALTERTABLE_ADDCOLS event from the HMS Hook side. This behaviour is observed only when the queries are run from Spark SQL and not when run the same queries are run from Beeline.

CDPD-39197: Debug metrics returns empty data
When debug metrics is enabled and some operations are performed, the response is empty
CDPD-36495: Updating legacyAttribute from False to True resets the initially created relationshipAttributes values
Creating types, entities, and to start, you must set the relationship with is_legacy_attribute value as False.

Later, update the value relationshipDef is_legacy_attribute to True.

For the entities that were created before updating the is_legacy_attribute to True, the relationshipAttributes value is reset.

CDPD-13466: Bulk create/update entity POST API does not create / update authorised entities
The bulk API fails with 403 error if some belong to entities on which the user is unauthorized and other GUIDs belong to entities on which user is authorized.
CDPD-22744: Bulk entity DELETE API does not delete authorised entities
Bulk entity DELETE API does not delete authorised entities when the list of authorised and unauthorised entities list is passed.
CDPD-29409: Hive import: Suggestion suggests entity which is deleted.
Suggestions suggests tables of a database, which is a deleted entity.
CDPD-25152: Tag propagation through deferred actions consumes additional time as compared to default flow
The additional time might be due to the small overhead added to create / update task vertex and which is run in the background. This also depends on number of tasks queued to be executed.
CDPD-42954: Zepplin notebook fails after enabling Atlas-HDFS hook

The Zeppelin notebooks are failing with errors after enabling Atlas-HDFS hook in the CDP cluster.

When the below properties are set for atlas-client.properties in Cloudera Manager:
  • atlas.jaas.KafkaClient.option.keyTab
  • atlas.jaas.KafkaClient.option.principal

Along with adding the properties in /etc/atlas/conf/atlas-application.properties, Cloudera Manager also adds these properties to atlas-application.properties for other services (like Spark).

Adding these properties interferes with the normal flow of the services (like Spark)

To enable HDFS lineage feature, instead of setting these properties through Cloudera Manager, users can manually add the properties directly in /etc/atlas/conf/atlas-application.properties
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-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-67022: Imports fail with 403 error by users with export, import permissions but without create, read, write, and update entity permissions
After the import is successfully executed, Atlas creates an entity of type _{}AtlasAuditEntry{} which eventually throws an _UNAUTHORIZED_ACCESS error with 403 status code since the user does not have permission to create, read, write or update entities.
Add a write permission for entity type _{}AtlasAuditEntry{_} to overcome this issue.
CDPD-67020: Imports fail by users with export or import permissions but no other permission for entities
As a part of the export service:
  1. The AtlasServerService creates a new AtlasServer entity if it does not exist already.
  2. The xportImportAuditService creates an entity with type __ExportImportAuditEntry If adequate read and write permissions are not present for the mentioned entities, exceptions are thrown and the creation of the atlas-export-result.json is skipped in the flow. This results in the service returning the response code 200. Subsequently, import with this export throws a Null Pointer Exception due to the missing atlas-export-result.json.
Ensure that the entity permission for AtlasServer and __ExportImportAuditEntry is present.
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.
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.
CDPD-71482: BCFKS keystore type is not recognized by the Atlas client
The Schema Registry - Atlas integration fail on the FIPS environment because the BCFKS keystore type is not recognized by the Atlas client. Currently, it is hard-coded as "JKS".
CDPD-66563: Atlas Import failing with "Invalid instance creation/updation parameters passed”
Importing external Hive tables using the Atlas API fails with the “Invalid instance creation/updation parameters passed” error.
The issue can be fixed by removing incomplete attribute validation.
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.
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.
CDPD-59565: Whole lineage becomes hidden when filters are enabled with deleted entity
When a larger lineage structure contains a circular lineage and this circular lineage contains at least one deleted entity, the whole lineage structure becomes hidden if both of the following filters are used:
  • Hide Processes
  • Hide Deleted Entities
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.