Known Issues in Apache Atlas

Known issues identified in Cloudera Runtime 7.3.2

OPSAPS-76330: Missing request/process context ID in Atlas logs after migration from log4j2 to logback using CM default pattern

7.3.2 and its SPs and CHFs

After upgrading Apache Atlas logging from log4j2 to logback, and using the default logback pattern provided by Cloudera Manager, Atlas logs no longer consistently include the request/process context ID (for example, etp<timestamp>-<pid> - <uuid>). This results in a regression compared to earlier behavior with log4j2, where the context ID was consistently present for request-scoped operations. The missing context information makes troubleshooting and tracing individual requests more difficult.

None

CDPD-91624: Performance degradation: Atlas Replication is 3-4x slower in 7.3.2 compared to 7.1.9

7.3.2

A performance degradation has been observed in the Atlas table replication process after upgrading from version 7.1.9 to 7.3.2. The average time to replicate a single table has increased by approximately 300-400%. In version 7.3.2, the replication takes 3-4 seconds per table, compared to approximately 0.94 seconds per table in version 7.1.9 (calculated from 0.11s export + 0.83s import). This significant slowdown affects the time required to complete Atlas replication operations for large-scale table replication, with tests showing that only 24,000 out of 100,000 tables were replicated in more than 40 hours.

None

OPSAPS-75853: Composite replication (Atlas + Iceberg) history entries recorded with "Partial success"

7.3.2 and its SPs and CHFs

When running composite replication operations that include both Atlas metadata and Iceberg data replication, the replication history entries are recorded with a status of Partial success even when the replication completes successfully. This can cause confusion about the actual status of replication operations.

Verify the actual replication status by checking the detailed logs and target system to confirm whether the replication completed successfully despite the Partial success status.

None

CDPD-96774: Entities not created in Atlas when Hive table created on top of OFS bucket/volume

7.3.2 and its SPs and CHFs

When a Hive table is created with data stored directly on an Ozone File System (OFS) bucket or volume (without a key path), the corresponding entities are not created in Apache Atlas. Only Hive tables created with OFS key-based paths (for example, ofs://serviceId/volume/bucket/key) are properly tracked in Atlas. Tables pointing directly to buckets (for example, ofs://serviceId/volume/bucket) or volumes (for example, ofs://serviceId/volume) do not generate Atlas entities, preventing metadata tracking and governance for these storage configurations.

Apache JIRA: ATLAS-5034

None

CDPD-95669: React UI: Entity type clicked in Basic Search results redirects to Home page instead of triggering type search

7.3.2 and its SPs and CHFs

In the React-based Atlas user interface, when you perform a basic search that returns multiple entities and click an entity type in the Type column of the search results table, the interface incorrectly redirects to the Home page instead of remaining on the Basic Search page and triggering a new search filtered by that entity type. This navigation behavior breaks the expected workflow and makes it difficult to refine searches based on entity types directly from the search results.

Use the Advanced Search feature to filter results by entity type, or manually enter the type filter in the Basic Search interface before performing the search.

Apache JIRA: ATLAS-5172

CDPD-95658: React UI: isIncomplete Property not visible in React UI for shell entities

7.3.2 and its SPs and CHFs

When viewing shell entities in the React user interface, the isIncomplete property is not displayed, even though the same entity shows this property correctly in the Classic user interface. This inconsistency prevents users from identifying incomplete entities when using the React interface. Shell entities are placeholder entities created with minimal metadata, and the isIncomplete property indicates that these entities require additional information to be complete. The React user interface now displays the isIncomplete property consistently with the Classic user interface, allowing users to identify shell entities regardless of which interface they use.

None

Apache JIRA: ATLAS-5170

CDPD-63922: RowTooBigException when reading and writing data to HBase

7.3.2 and its SPs and CHFs

When Atlas performs operations that read or write large amounts of data to HBase through JanusGraph, a RowTooBigException can occur if the row size exceeds the configured maximum row size limit (hbase.table.max.rowsize). This exception has been observed in multiple escalations during operations such as patch application, advanced search, and entity creation. The error indicates that the row data being processed is larger than the allowed maximum (typically 1GB or 2GB depending on configuration). While increasing the hbase.table.max.rowsize property can help in some cases, it may also cause out-of-memory errors on the HBase side. The root cause is related to how JanusGraph stores data in HBase and requires deeper investigation of Atlas data storage patterns.

As a temporary workaround, you can increase the hbase.table.max.rowsize property value. However, be aware that significantly increasing this value may lead to out-of-memory errors in HBase. Monitor HBase memory usage after making this change.

CDPD-94690: React UI: Classification searches parent classification instead of child

7.3.2 and its SPs and CHFs

When using the React user interface to search for entities by classification, clicking the Search option on a sub-classification incorrectly triggers a search for the parent classification instead of the selected sub-classification. This causes users to see search results for the wrong classification hierarchy level, making it difficult to find entities tagged with specific sub-classifications. The search now correctly uses the selected sub-classification, returning accurate results that match the user's intended search scope.

None

Apache JIRA: ATLAS-5168

CDPD-92014: React UI: Fix UI layout issue for tables when no records are present

7.3.2 and its SPs and CHFs

When viewing tables in the React UI Search and Business Metadata sections with no records, the table headers appear visually constrained or misaligned. This layout inconsistency affects the user interface appearance and makes empty result screens look unprofessional. The table headers now display with proper alignment and layout even when no records are present, ensuring a consistent and polished user experience across all data states.

None

Apache JIRA: ATLAS-5151

CDPD-91961: Import failure due to missing support for handling multiple relationship types under a single attribute

7.3.2 and its SPs and CHFs

When importing entities where a single relationship attribute (such as hive_db.tables) contains a mix of different entity types (for example, both hive_table and iceberg_table references), the import operation may fail or produce incomplete relationship graphs. Atlas incorrectly derives only one relationship type for the entire collection, typically hive_table_db, which causes relationship validation to fail for other entity types like iceberg_table. This data-dependent issue is difficult to diagnose and can result in import errors or missing Iceberg table relationships. Atlas logs may show errors about invalid relationship end types or invalid relationship definitions for specific elements within a relationship attribute.

None

Apache JIRA: ATLAS-5156

CDPD-87879: Moving an Iceberg table from one database to another database is creating incomplete entity

7.3.2 and its SPs and CHFs

When renaming an Iceberg table to move it from one database to another using the ALTER TABLE statement with RENAME TO clause (for example, ALTER TABLE test_share.iceberg_table RENAME TO default.iceberg_table), an incomplete entity is created in the target database. This occurs because the Hive Metastore hook incorrectly classifies the operation as an ADDPROPS (add properties) operation instead of a RENAME operation for Iceberg tables. This misclassification causes the HMS hook to process the event incorrectly, passing only the DO_NOT_UPDATE_STATS = true property while omitting critical properties such as old_table_name, alterTableOpType = RENAME, and old_db_name that are required for proper entity handling. As a result, Atlas creates an incomplete entity in the target database rather than properly renaming the existing entity.

None

CDPD-99217: Incomplete Metadata Display for Ozone Buckets in Atlas Search Results

7.3.2 and its SPs and CHFs

While searching for certain Ozone buckets in the Atlas UI, the results page loads, but key details such as Properties, Classifications, Relationships, and Audits are not displayed. The issue stems from the large size of the response payload, specifically the relationships section, which exceeds 500MB in the JSON response. This overwhelms the UI, preventing it from rendering associated metadata.

None

Apache JIRA: ATLAS-5184

CDPD-91959: Entities not created in Atlas when hive table created on top of a OFS bucket/volume

7.3.2 and its SPs and CHFs

In Atlas, key based tables are created properly. However, bucket/volume based tables do not show up in Atlas. When trying to create hive tables on top of ozone OFS buckets/volumes, the entities are not created.

None

Apache JIRA: ATLAS-5034

CDPD-89476: need to enhance the repair_index.py script

7.3.2 and its SPs and CHFs

When executing the repair_index.py script provided by Cloudera to reindex Atlas metadata, the script fails to run under Java 17, which is now commonly used in customer environments. Customers upgrading their OS or JVM to OpenJDK 17 encounter errors related to java.lang.reflect.InaccessibleObjectException. Even after bypassing this with additional JVM flags, the script later fails with Keystore was tampered with, or password was incorrect. This indicates potential mismatches with the Java version, keytool compatibility, or the way the script selects runtime process directories and handles credentials.

Short-term workaround:

• Add the following JVM options in repair_index.py to bypass JPMS restrictions in Java 17:

  --add-opens=java.base/java.lang=ALL-UNNAMED \
                  --add-opens=java.base/java.lang.reflect=ALL-UNNAMED

• Manually verify and specify the correct conf and keystore directory to avoid loading stale credentials.
• Run the script under Java 8 or Java 11 if possible.

CDPD-88306: Atlas UI: Iceberg tables are not visible in the Relationships tab

7.3.2 and its SPs and CHFs

On the Atlas user interface, the Relationship tab for a database entity is not displaying Iceberg tables when both Hive and Iceberg tables are present in the same database. While Hive tables are visible as expected, Iceberg tables are missing from the visualization. If only Iceberg tables exist in the database, they are displayed correctly in the Relationships tab.

None

CDPD-78683: Standalone Atlas replication fails when unexpected inputs are provided

7.3.2 and its SPs and CHFs

When a standalone Atlas replication policy is created for NULL or hive_db entity types, and no Hive or Iceberg tables are created, the replication fails with a generic exception (Atlas Export operation has failed. Please check role logs for more info.) instead of either skipping the operation (NOOP) or providing a descriptive error message about the problematic inputs. This generic error message can be misleading.

None

CDPD-76686: Concurrent Ingestion: doesn't commit the kafka offset

7.3.2 and its SPs and CHFs

When concurrent processing is enabled ( atlas.notifications.concurrent=true), Atlas processes messages efficiently but may fail to commit the Kafka offset. This results in the current offset getting stuck for an extended period, despite the messages being processed successfully.

None

CDPD-77640: Inconsistent results from global search due to case sensitivity

7.3.2 and its SPs and CHFs

Global search in Atlas produces inconsistent results based on the case of the search term. Searching with a lowercase term returns the expected entities, whereas searching with the same term beginning with an uppercase character does not return the same results. This issue is related to case-sensitivity handling in the search layer, likely in indexing or query processing.

None

Known issues identified before Cloudera Runtime 7.3.2

Known issues identified before Cloudera Runtime 7.3.2 include only unresolved issues from previous releases that continue to affect the Cloudera Runtime 7.3.2 base release.

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, 7.1.9 SP1 CHF15 through 7.1.9 SP1 CHF4

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, 7.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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-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.1.9 SP1 and its SPs and CHFs

The ddlQueries and outputFromProcesses (lineage) is missing for the alter queries.

Apache JIRA: ATLAS-4747

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.1.9 SP1 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.1.9 SP1 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, 7.1.9 SP1 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, 7.1.9 SP1 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-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, 7.1.9 SP1 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, 7.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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, 7.1.9 SP1 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, 7.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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

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-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

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.1.9 SP1 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, 7.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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.1.9 SP1 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