- CDPD-77738: Atlas hook authorization issue causing
HiveCreateSysDb timeout
- 7.3.2 and its SPs and CHFs, 7.3.1.700 through
7.3.1.100
- Atlas hook authorization error causes
HiveCreateSysDb command to time out due to repeated retries.
- None
- CDPD-69150: Unable to add labels or user defined properties in
Japanese
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs
- 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
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-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.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-62973: Change in audits behavior in Cloudera Runtime 7.2.18 deployment.
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHF, 7.2.18 and its SPs and CHFs
- 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.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- The ddlQueries and outputFromProcesses (lineage) is missing for
the alter queries.
-
Apache JIRA: ATLAS-4747
- CDPD-77257: When a HIVE CTAS Iceberg table is created, an extra
"staging" HDFS path created is also in Apache Atlas
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHF7.2.18 and its SPs and CHFs, 7.3.1.100 and subsequent CHFs and SPs
- 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.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18.600 and its SPs and CHFs
- 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-69140: Incremental export: When an entity has tag
propagated and is exported, the tag is not propagated to it in the export
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs
- When creating tables with multiple levels of depth, a tag
applied to the first table will be propagated along the lineage. After exporting the
last table, it will not have the propagated tag.
-
Apache JIRA:
ATLAS-4889
- CDPD-77128: Log out message for Atlas needs to be more
informative on Knox enabled cluster
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs
- Logging out of Atlas does not manage the external
authentication. 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 additional access to Atlas, close all browser
windows and exit the browser.
- CDPD-59850: Partition specification data for Iceberg table is
not getting updated in atlas using Impala for Spark created table
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- The specification data sent to Atlas after Spark creates
an Iceberg partitioned table is reflected in the Atlas UI. However, it is not reflected
in Atlas after a partition specification update using the Impala shell.
- CDPD-83398: REMOVE_LEGACY_REF_ATTRIBUTES Patch Skipped During
Startup, Causing Errors While Processing DML Events
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHF
- The
REMOVE_LEGACY_REF_ATTRIBUTES patch
is skipped during Atlas patch processing, which leads to an error when Data Manipulation
Language (DML) events (e.g., "insert data") are processed, events that are typically
ignored. This is observed in environments where DML event filtering is not in place or
the patch is not applied correctly. As a result, Atlas attempts to process these events
and encounters errors related to missing or outdated attribute handling.
- CDPD-88230: Bulk import operations currently do not construct
lineage as expected
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs
- Bulk import operations do not create lineage
consistently, even when the entities are imported successfully.
- CDPD-88302: Bulk import operations currently do not create
audits for the imported entities
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs
- Bulk import operations do not create audits for the
imported entities.
- CDPD-7982: HBase bridge stops at HBase table with deleted column
family
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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
-
Apache JIRA:
ATLAS-3551
- CDPD-6675: Irregular qualifiedName format for Azure storage
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-922: IsUnique relationship attribute not honored
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-1664: Guest users are redirected incorrectly
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-1823: Queries with ? wildcard return unexpected
results
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-1884: Free text search in Atlas is case sensitive
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-1892: Ranking of top results in free-text search not
intuitive
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-3125: Logging out of Atlas does not manage the external
authentication
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-3160: Hive lineage missing for INSERT OVERWRITE
queries
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-3208: Table alias values are not found in search
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-4545: Searches for Qualified Names with "@" doesn't fetch
the correct results
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-4762: Spark metadata order may affect lineage
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-10574: Suggestion order doesn't match search weights
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs
- At this time, the order of search suggestions does not honor the
search weight for attributes.
- None
-
Apache JIRA: ATLAS-3081
- CDPD-10576: Deleted Business Metadata attributes appear in
Search Suggestions
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs
- Atlas search suggestions continue to show Business Metadata
attributes even if the attributes have been deleted.
- None
-
Apache JIRA: ATLAS-3739
- CDPD-11692: Navigator table creation time not converted to
Atlas
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- In converting content from Navigator to Atlas, the create time
for Hive tables is not moved to Atlas.
- None
-
Apache JIRA:
ATLAS-3739
- CDPD-11940: Database audit record misses table delete
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-11941: Table creation events missed when multiple tables
are created in the same Hive command
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-55122: Any user with ssh access can view the downloaded
results
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- When a user triggers a download from the Atlas user
interface, the downloaded data can be viewed by any other user who has SSH access to the
host. This occurs because the downloaded files are not sufficiently restricted by file
permissions on the local filesystem, allowing unintended access to potentially sensitive
data.
- None
- 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,
7.3.1.500, 7.3.1.600
- During an availability zone (AZ) outage, if an Atlas
server host becomes unreachable or is stopped, Atlas requests routed through Knox
experience a significant delay before failing over to an available host. The requests
may attempt multiple failovers for approximately four minutes (taking about two minutes
for each failover attempt) before either failing or eventually reaching an active Atlas
server.
- None
- CDPD-67112: Import transforms do not work as expected when
replacing a string which already has "
:"
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- The character “
:” is not supported in path
replacements. The import succeeds but location remains unchanged. The character “
:” must be avoided.
- None
-
Apache JIRA: ATLAS-4834
- CDPD-56590: Create table "like" from Iceberg table creates a
hive_table instead of iceberg_table
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- 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-68191: Suggestions do not return the correct results when
searching multiple Chinese characters
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs
- Free text search does not return results when searching Chinese
phrases made of multiple characters. Partial searches return the correct results.
- None.
- CDPD-77434: Search suggestions may fail to return results when
using complete qualified names in RAZ-enabled environments
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- When performing searches in the Atlas UI or through the
REST API using a complete qualified name as the prefix string (for example, searching
for an Iceberg column using its full qualified name), the suggestions API sometimes
fails to return the expected entity in the suggestions list, even though the entity
exists and would be returned in the actual search results. This issue occurs
consistently in RAZ-enabled AWS clusters but has not been observed in IDB (internal data
bus) or Cloudera on prem clusters. The behavior is intermittent: the REST API
/api/atlas/v2/search/suggestions?prefixString=<complete_qualifiedName>
may return an empty suggestions array ({"suggestions": []}), while the
same entity appears correctly when searched through the user interface. This
inconsistency affects user experience and makes entity discovery less reliable in
RAZ-enabled environments.
- None
- CDPD-81499: Basic search performance degradation when filtering
on boolean attributes
- 7.3.2 and its SPs and CHFs, 7.3.100 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- When performing basic searches with filters on boolean
attributes (for example,
isDisposed = true), search operations may
experience significant performance degradation, particularly with large datasets. This
occurs because boolean datatype attributes are not indexed in Solr and require in-memory
filtering in Atlas. When the search API attempts to return the requested number of
results (for example, limit of 25), it repeatedly queries Solr for active entities and
then filters them in Atlas based on boolean attribute values. This causes Atlas to
traverse through potentially large numbers of entities until it finds enough matches,
resulting in increased search times as data volume and query offset increase. Atlas logs
may display warnings such as: not using index-search for attribute
EntityType.booleanAttribute; might cause poor performance.
- None
- CDPD-69317: Export/Import API: When tag attributes types get
modified between the exports, causes issues in import
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- When using the Export/Import API, if a tag's attribute
type is modified (for example, from string to double) between incremental exports, the
import operation on the target cluster fails due to the difference in attribute types.
- None
- CDPD-65906: Export: When relationship is updated to block tag ,
the imported lineage doesn't have the updated relationship
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and
CHFs, 7.2.18 and its SPs and CHFs
- When using the Export/Import API to migrate data between
clusters, if a relationship between entities is modified to block tag propagation (for
example, setting propagation from table to process as 'None') and a tag is subsequently
added, the tag correctly does not propagate on the source cluster. However, after
exporting to the target cluster, the relationship on the target cluster does not reflect
the blocked propagation, and the tag incorrectly propagates to the related entities.
- None
-
Apache JIRA: ATLAS-4833
