Known Issues in Apache Atlas
This topic describes known issues and workarounds for using Atlas in this release of Cloudera Runtime.
- Search Returns Unexpected Results for New Entity Definitions with BigInteger or BigDecimal Attributes
- When new entity types are defined with BigInteger or BigDecimal type attributes, searches against values in any attributes in entities of these types return unexpected results.
- Atlas custom properties ignored in client services
- When adding a custom property for the atlas-application.properties in Atlas hook-based services such as Hive, HBase, and Impala, the custom property is not reflected in the actual configuration file that Cloudera Manager generates, causing these properties to be ignored.
- 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.
- 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.
- Missing Impala and Spark lineage between tables and their data files
- Atlas does not create lineage between Hive tables and their backing HDFS files for CTAS processes run in Impala or Spark.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Extra WARN messages from Solr in the Atlas log
- Communication between JanuGraph and Solr for some entity attributes included in the search index produces a large number of WARN messages in the Atlas logs. Other than increasing the volume of messages in the logs, no functionality is affected.
- 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.
