Homepage

Cloudera Base on premises 7.3.2 Release Summary

Cloudera is excited to announce the General Availability (GA) and delivery of Cloudera Runtime 7.3.2! Building on the milestone unified release of Cloudera 7.3.1, this version represents the most enduring Long-Term Support (LTS) release to date, with guaranteed support extending through 2032.

While version 7.3.1 established the first-ever unified code base for both Cloudera on-cloud and Cloudera Base on-premises, version 7.3.2 hardens this hybrid foundation to support your long-term hybrid cloud strategy. This release delivers the stability, performance, and security required to sustain an enterprise data strategy through the full support lifecycle. By upgrading to 7.3.2, you leverage the accelerated innovation of a unified platform while securing a “safe harbor” for your most critical production workloads.

Main highlights of this release

  • Cloudera Lakehouse Optimizer: By optimizing Iceberg within Cloudera on-premises, Cloudera now delivers query performance that is 38 times faster and reduces storage costs by up to 36%.

  • Cloudera Data Sharing: This capability maintains data gravity and governance within Cloudera while sharing Iceberg table data with external platforms, such as Databricks and Snowflake, through Apache Iceberg REST Catalog APIs.

  • Cloudera Object Store powered by Apache Ozone: Enhancements in Ozone improve metadata handling, cluster coordination, and diagnostic tooling, providing deeper insights into cluster health.

  • Cloudera Cloud Bursting: This breakthrough in hybrid data management introduces a hybrid-native foundation that removes the complexity of fragmented management and eliminates costly workload migrations.

  • Enhanced Data Security and Scalability: This release improves platform resilience by integrating the latest open-source rebases and IPv6 support. It resolves more than 90 critical and high CVEs to ensure a secure environment for AI workloads.

Key Benefits and Upgrade Path Impact

This release acts as a critical bridge for customers who want to move away from the risks of aging infrastructure to a modern, high-performance foundation. By upgrading to 7.3.2, you gain advanced AI capabilities, stronger security, and guaranteed support for several years.

Current Version Why It Matters Bottom Line
7.1.7 (EOS) You are operating on End-of-Support software without official support or security patches. 7.3.2 provides a modern "safe harbor" that restores full support and compliance through a direct in-place upgrade.
7.1.9 (LTS until 2028) While 7.1.9 remains supported until 2028, 7.3.2 optimizes performance for modern data workloads and AI readiness. Stay on an LTS path while gaining the performance required for high-scale AI and modern data workloads.
7.3.1 (STS until 2026) Version 7.3.1 reaches End-of-Support later this year. Move to 7.3.2 now to lock in years of stability and avoid another upgrade cycle this winter.
7.2.18 (Cloudera on cloud) Public Cloud environments demand the highest levels of security and operational efficiency. 7.3.2 delivers better performance, lower Total Cost of Ownership (TCO), and reduced monthly credit spend.

Supported Upgrade Paths

Clusters running the following releases support a direct, one-step, in-place upgrade to Cloudera Runtime 7.3.2:

  • 7.1.7 SP3
  • 7.1.9 SP1
  • 7.3.1
  • 7.2.18

Using Cloudera Manager 7.13.2, these direct paths utilize pre-check validations and component-specific improvements to reduce downtime. If you use other versions, you must first upgrade to a supported “bridge” version before moving to 7.3.2.

Key Features

  • IPv6 Support: Cloudera now enables IPv6 client-side support for Cloudera Data Explorer (Hue), Kafka, Phoenix, Kudu, Hive, ZooKeeper, HBase, and Impala. As part of the 7.3.2 roadmap, Cloudera plans to enable IPv6 for all remaining components over the next several years.

  • JDK Updates: Cloudera now uses JDK 17 as the default standard. This release removes support for JDK 8 and JDK 11 to improve security and speed.

  • Cloudera Cloud Bursting: Dynamically and temporarily extend your private data center into the cloud to unlock on-demand elasticity without data duplication.

  • Cloudera Lakehouse Optimizer: This tool uses smart automation to maintain Iceberg tables. It includes easy scaling, flexible scheduling, and Ranger integration.

  • Automated Data Lifecycle Management with Ozone: (Technical Preview) Save up to 50% physical storage by converting 3-way replicated blocks to erasure coding.

Additional features and highlights

  • Component Rebases: Cloudera updates core components such as Hadoop 3.4, Kafka 3.9, Atlas 2.4, Knox 2.1, Ranger 2.6, Spark 3.5, Zookeeper 3.8, Phoenix 5.2.1, and HBase 2.6.3.

  • Atlas Features: Atlas now uses a ReactJS-based UI instead of BackboneJS. This update provides a simpler interface and a more reliable experience. In technical preview, Atlas also supports automatic purging of deleted items. This keeps metadata clean and improves speed by removing old data on a schedule.

  • Ranger RAZ: Ranger RAZ now supports S3A-compatible object stores for Cloudera Base on premises with ID Broker. This provides consistent, This feature delivers consistent, fine-grained security across all deployments.

  • Replication Manager: Cloudera now supports Iceberg replication across AWS regions. Other features include on-premises replication for Ozone storage and Atlas replication for Hive external tables and Iceberg. This release also adds Ranger on-premises to cloud replication for hybrid control and FIPS 140-2 compliance for better security.

  • Cloudera Data Explorer: Hue evolves into Cloudera Data Explorer, marking the first step in product growth and UI improvements.

  • Impala: Cloudera delivers the following improvements for Impala in 7.3.2:

    • Intermediate results caching now uses encryption to boost speed.

    • Lazy materialization to scan Parquet files faster.

    • Hierarchical event processing improves catalog quality.

    • OpenTelemetry integration improves observability reporting.

    • Iceberg diagnostic metrics in Query Profiling enable better tuning.

    • AES encryption and decryption improve data security.

    • Cloudera certifies on premises S3-compatible object stores.

    • Impala now supports ARM-based processors.

  • Kudu: Cloudera delivers the following improvements for Kudu in 7.3.2:

    • Kudu now supports ARM-based processors.

    • The addition of the new Array data type expands data flexibility.

    • Flink-based tools now enable real-time replication.

    • Cloudera simplifies Python integration for easier development.

    • Enhanced configurations increase cluster density.

    • Improved memory tracking prevents out-of-memory errors.

  • HBase: Cache persistence resilience improves upgrade stability.

  • Phoenix now supports High-Availability (HA) configurations.

  • Solr: Cloudera adds ARM architecture support for Data Hub and updates the HBase Indexer to match the 2.6.3 version.

  • Hive: Cloudera delivers the following improvements for Hive in 7.3.2:

    • Hive enhances Iceberg v2 functionality.

      • New Branching and Tagging capabilities.

      • Users can now expire snapshots to manage storage.

      • Hive supports the TRUNCATE PARTITION command.

      • Hive supports INSERT INTO and INSERT OVERWRITE PARTITION operations.

      • Copy on Write functionality.

      • The Iceberg RESTful API now supports HMS.

      • Hive supports the DROP PARTITION command.

      • Improves Compaction support.

    • The Cost-Based Optimizer (CBO) improves Common Table Expression (CTE) performance.

    • Hive now runs on hosts with ARM architecture.

    • OpenTelemetry (OTEL) integration improves Hive observability.

Compatibility and Certifications

Data Services Compatibility

To ensure a smooth transition and a fully supported environment, follow these essential compatibility requirements.

Cloudera Runtime 7.3.2 integrates with Cloudera Data Services on premises 1.5.5 SP1, 1.5.5 SP2, and Cloudera Manager 7.13.2.

Cloudera Base on premises 7.3.2 supports only Cloudera Data Services on premises versions 1.5.5 SP1 (excluding Cloudera AI) and 1.5.5 SP2 (excluding Cloudera AI). Upgrade your Cloudera Data Services on premises to one of these supported versions before you install or upgrade to Cloudera Base on premises 7.3.2.

Do not install or upgrade to Cloudera Base on premises 7.3.2 if you run Cloudera Data Services on premises 1.5.5 (all services) or versions 1.5.5 SP1 or 1.5.5 SP2 with Cloudera AI on your cluster, as these versions are incompatible for Spark pushdown use cases.

New Operating Systems and Database Certifications

Cloudera now certifies the following operating systems and databases:

  • Operating Systems: RHEL 9.6, Rocky Linux 9.6, Ubuntu 24.04, SLES 15 SP6
  • Databases: MariaDB 11.4

End of Support for Operating Systems, Databases, and Environments

Cloudera Manager 7.13.2 removes support for several operating systems, databases, Python versions, and Java Development Kits (JDKs). To ensure a successful upgrade, verify that your environment meets these updated requirements.

Database Support

Cloudera no longer supports the following databases:

  • PostgreSQL 13
  • Oracle 19c (including 19c RAC)

Operating System Support

Cloudera no longer supports the following operating systems:

  • SLES 15 SP4
  • Ubuntu 20.04

Python Support

Cloudera Manager 7.13.2 limits Python compatibility to modern versions, and now only supports Python 3.11. Consequently, Cloudera has removed support for:

  • Python 3.8
  • Python 3.9
  • Python 3.10

JDK Support

To improve performance and security, Cloudera Manager 7.13.2 consolidates Java support, and now only supports JDK 17. Consequently, Cloudera has removed support for:

  • Azul JDK 8, OpenJDK 8, and Oracle JDK 8
  • Azul JDK 11, OpenJDK 11, and Oracle JDK 11

API Compatibility Matrices

Cloudera now provides API Compatibility Matrices documentation for Cloudera Manager and Cloudera Runtime.

These matrices facilitate seamless communication between automated clients and servers by defining required Python environments and minimum version alignments. They establish backward and client-server compatibility to ensure software components function correctly and remain stable as system environments evolve.

Resources for this release