Known Issues in Apache Atlas
Learn about the known issues in Atlas, the impact or changes to the functionality, and the workaround.
- CDPD-48122: Support for the sortBy parameter under - api/atlas/admin/audits API is not available. Therefore, audit results under the administration audit page are working with limitations. You cannot sort the administration audit results.
- None
- CDPD-29307: Atlas creates incomplete Kafka client entities that are postfixed with the metadata namespace.
- None.
- CDPD-19358: "IsIndexable"and "isOptional" value of a typedef's attribute is modified post migration.
- None.
- CDPD-22799: Apache Atlas displays 503 service unavailable on transparent proxy setup.
- In the following file /opt/cloudera/parcels/CDH-<%version%>/lib/atlas/server/webapp/atlas/WEB-INF delete DOCTYPE tag, and replace web-app tag with following: <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5">
- OPSAPS-58348: The user name HTTP is not found in Atlas logs
- You must disable the Atlas metrics configuration from Cloudera Manager UI.
- CDPD-19996: Atlas AWS S3 metadata extractor fails when High Availability is configured for IDBroker.
- If you have the HA configured for IDBroker, ensure that your cluster has only one IDBroker address in core-site.xml. If your cluster has two IDBroker addresses in core-site.xml, remove one of them, and the extractor must be able to retrieve the token from IDBroker.
- CDPD-5542: AWS S3 Bulk and Incremental Extraction is currently not supported on 7.1.5.
- None.
- CDPD-17355: Atlas AWS extraction issue due to KeyError: 'entities'.
- AWS S3 extraction does not happen as the extractor.sh is missing from the host.
- CDPD-14877:
- In the Ozone Atlas integration, only the Spark-Atlas connector is failing.
- CDPD-12668: Navigator Spark lineage can fail to render in Atlas
- As part of content conversion from Navigator to Atlas, the conversion of some spark applications created a cyclic lineage reference in Atlas, which the Atlas UI fails to render. The cases occur when a Spark application uses data from a table and updates the same table.
- CDPD-54865: Atlas server does not come up due to circular dependency in TaskRegistry class and throws errors
- The errors pointed to a circular dependency issue which was caused
by TaskRegistry
class(
repository/src/main/java/org/apache/atlas/tasks/TaskRegistry.java
) - 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.
- 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.
- CDPD-11790: Simultaneous events on the Kafka topic queue can produce duplicate Atlas entities
- In normal operation, Atlas receives metadata to create entities from multiple services on the same or separate Kafka topics. In some instances, such as for Spark jobs, metadata to create a table entity in Atlas is triggered from two separate messages: one for the Spark operation and a second for the table metadata from HMS. If the process metadata arrives before the table metadata, Atlas creates a temporary entity for any tables that are not already in Atlas and reconciles the temporary entity with the HMS metadata when the table metadata arrives.
- 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.
- 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. - CDPD-10576: Deleted Business Metadata attributes appear in Search Suggestions
- Atlas search suggestions continue to show Business Metadata attributes even if the attributes have been deleted.
- 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.
- 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.
- 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""})
- CDPD-7781: TLS certificates not validated on Firefox
- Atlas is not checking for valid TLS certificates when the UI is opened in FireFox browsers.
- 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 dohdfs_path
entities in other location types. - 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 the 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- OPSAPS-58720: Atlas HBase hook not enabled post migration to CDH
- Using the AM2CM tool for HDP-2 to CDP-7, post-migration, you must manually enable the Atlas HBase hook.
- OPSAPS-58784: HMS hook is not enabled by default
- Using the AM2CM tool for HDP-2 to CDP-7, post-migration, you must manually enable the Atlas HMS hook.
- CDPD-23776: When a HBase table is dropped, the relationship between the table and namespace is displayed as ACTIVE
- When the HBase table is disabled and dropped, the table status is marked DELETED but the relationship status between table and namespace is still ACTIVE.
- CDPD-23587: hbase_namespace owner is updated to user who creates the HBase table
- Owner of the HBase namespace must not be modified based on users' who create the table under it.
- CDPD-22484: DML statements like "insert" and "delete" are captured by Atlas
- Extra audits are generated by Atlas for DML statements on tables like insert and delete values on the table.
- CDPD-27390: [Entity Audits] 'Propagated Classification Added' timestamp is < 'Entity Created' timestamp
- The 'Propagated Classification Added' timestamp is < 'Entity Created' timestamp. This is invalid since the classification is propagated once the entity is created.
- CDPD-28026: [Atlas: Debug Metrics] Debug metrics is empty on cluster with Custom Principal
- Debug metrics is fetched 30 seconds after an operation is performed. Later, there are no debug metrics available.
- 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