What's New in Apache Atlas

New features and functional updates for Atlas are introduced in Cloudera Runtime 7.3.2, its service packs, and cumulative hotfixes.

Cloudera Runtime 7.3.2 introduces new features of Atlas and includes all service packs and cumulative hotfixes from 7.3.1.100 through 7.3.1.706. For a comprehensive record of all updates in Cloudera Runtime 7.3.1.x New Features .

Cloudera Runtime 7.3.2:

New React-based user interface for Apache Atlas

Apache Atlas now features a redesigned React-based user interface (UI) that offers enhanced usability and streamlined metadata management. You can switch between the Classic and New UI experiences. The new interface introduces an improved search panel that automatically lists all available entity types, classifications, and glossary terms, with one-click access to relevant members. Enhanced filtering capabilities allow you to display empty service types, unused classifications, and toggle between category or term views in the glossary. Additionally, the interface displays entities and classifications in a collapsed flat tree view to simplify navigation of complex metadata hierarchies. For more information, see Apache Atlas dashboard tour.

Apache Atlas component upgraded to 2.4.0

The Atlas runtime component is upgraded from 2.1.0 to 2.4.0. Several stability and correctness fixes are included from the upstream release for bugs, including UI improvements for classification propagation settings.

Atlas auto-purging introduced

The automated entity auto-purging feature addresses potential performance and storage issues caused by the manual purge strategy. Previously, Atlas preserved metadata by only marking entities as deleted (soft-delete). This led to query performance degradation and increased storage usage as soft-deleted entities accumulated. While these entities could be manually deleted by using the PUT /admin/purge/ API call, the process failed to remove column lineage entities associated with soft-deleted process entities.

The new, cron-based system can clean up obsolete process entities, including their column lineage entities, that are no longer relevant. This prevents sparse graphs and significantly improves metadata hygiene and query performance. For more information, see Atlas Auto-Purging overview.

Atlas upgraded to use JDK 17

Atlas now runs on Java 17, upgraded from Java 8. JDK 17 is a Long-Term Support (LTS) release that brings improved performance, enhanced security, and better long-term maintainability. JDK 17 has the following key benefits for Atlas users:

Improved garbage collection, resulting in lower latency and more efficient memory usage for metadata-intensive workloads.
Stronger cryptographic algorithms reducing security vulnerabilities.
Long-term support guaranteed until at least 2029, ensuring continued security patches.

Logback introduced as logging framework

Apache Atlas now uses Logback as its logging framework, replacing Log4j2. This change enhances security and simplifies log management. It also enables you to add any new properties overriding existing properties.

The new logging framework provides simplified configuration by using native XML configuration instead of the .properties file.

Go to Cloudera Manager > Atlas Server XML Override to replace the complete configuration file.

Configuration values for file size and rotation remain the same.