Fixed issues in Atlas

Cloudera Runtime 7.3.3

CDPD-109807: Async import queue permanently blocked after JanusGraph transaction failure

7.3.3

When a JanusGraph transaction commit failed during asynchronous metadata import, the import queue could remain blocked and later import requests stayed in the WAITING state. Atlas now guarantees that import semaphores are released and requests are completed or failed reliably, even if persisting the failed state throws an exception or the executor is unavailable, ensuring the queue can process subsequent work.

Apache JIRA: ATLAS-5345

CDPD-106349: Atlas UI: Port Apache Atlas React UI upstream fixes

7.3.3

The React-based Atlas user interface now includes upstream fixes for the responsive header and Quick Search layout, glossary nested subcategories and subcategory creation, an upgraded sanitize-html dependency to mitigate cross-site scripting risk, Type System filter and lineage graph improvements, audit pagination and entity payload enrichment, frontend dependency updates, classification tooltip and search results table behavior, classification filter reset without HTTP 400 errors, Create Entity navigation on the entity detail page, text overflow in search filters and modals, audit filter toolbar layout, and build optimizations with lazy route loading.

Apache JIRA: ATLAS-5297, ATLAS-5298, ATLAS-5299, ATLAS-5301, ATLAS-5303, ATLAS-5305, ATLAS-5306, ATLAS-5328, ATLAS-5329, ATLAS-5330, ATLAS-5333, ATLAS-5339, ATLAS-5346

CDPD-110585: Atlas JanusGraph integration fails on JDK 21

7.3.3

Atlas JanusGraph integration failed on JDK 21 because reflective access to modify JanusGraph store manager internals threw an IllegalAccessException due to stricter field access restrictions. The fix restores JDK 21 compatibility by introducing a fallback utility that uses sun.misc.Unsafe to inject custom backend managers when standard reflection is blocked.

OPSAPS-78886: Atlas: Register new Single EKU parameters in the CM upgrade handler

7.13.2.30000

When you upgrade a cluster, Cloudera Manager now initializes new Atlas client keystore and server truststore configuration parameters for single end-entity certificate (Single EKU) support. On upgrade, new keys default to the existing dual end-entity certificate paths so behavior remains unchanged until you configure the split stores.