Atlas
This section lists the issues that have been fixed since the previous version.
- OPSAPS-53788: Lineage info for HBase not available in a TLS-enabled environment
- Atlas will not collect metadata from HBase (namespaces, tables, or column families) when Cloudera Manager is configured for TLS/SSL. This issue has no effect on HBase functionality, however, tag-based authorization through Ranger policies will not be available for HBase.
- CDPD-6023: Slight differences in metadata collected for Hive database entities depending on source
- When a Hive database is created using Beeline, the
ownerType
is sent to ATLAS_HOOK and in recorded in thehive_db
entity. However, when a Hive database is created through Spark-shell, theownerType
is missing in the Atlas entity. - OPSAPS-51224: 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. - CDPD-5314: Unexpected Results from Atlas Advanced Search Query with Underscore Character
- An Atlas Advanced Search with an equal operator (=) and a
like
operator where thelike
object includes an underscore does not return correct results. For example, the following search does not return expected results: - CDPD-5309: Unexpected Results from Atlas Advanced Search Query on String Attributes
- When new entity types are defined with string type attributes, Advanced Searches against the string attributes return unexpected results. For example, if attribute values include "caterpillar", "alleycat", and "altercation", all values are returned when searching for "cat*". The expected result would be that only "caterpillar" would be returned.