Cloudera CDP 7.3.2 Release Summary — A Long-Term Support Release Supported Through 2032 with Hybrid Cloud Capabilities

Cloudera Base on-premises 7.3.2, which reached GA in March 2026, is what Cloudera officially calls "the longest-lived LTS (Long-Term Support) release to date." It is guaranteed to be supported through 2032, and builds on the unified codebase from 7.3.1 by adding the capabilities a hybrid strategy needs — Lakehouse optimization, data sharing with external platforms, and cloud bursting.

This post summarizes the key changes in 7.3.2. The source is Cloudera's official Base on-premises 7.3.2 announcement.

---

1. 7.3.2 at a Glance

One-line summary: "A release aimed at legacy 7.1.x, 7.2.x, and 7.3.1 users that promises support through 2032."

---

2. Key Highlights

Cloudera Lakehouse Optimizer

A new component that automatically maintains and optimizes Iceberg tables.

• Up to 38× query performance improvement
• Up to 36% reduction in storage cost
• Smart automation for Iceberg maintenance work like compaction, snapshot expiration, and file cleanup
• Flexible scheduling and Ranger integration keep the permission model consistent

Think of it as platform-level absorption of the territory operators used to cover themselves by writing OPTIMIZE and EXPIRE SNAPSHOTS jobs and running them on cron.

Cloudera Data Sharing

Share Iceberg tables with external platforms like Databricks and Snowflake without data replication.

• Built on the standard Apache Iceberg REST Catalog API
• Preserves data governance (who sees what) and data gravity (the source data stays put)
• Mitigates the "copy proliferation" problem in multi-cloud, multi-engine environments

Cloudera Cloud Bursting

"Dynamically extend the private data center into the cloud."

• Keep the on-premises cluster as the base, and dynamically add cloud resources when workloads peak
• On-demand elasticity without data duplication
• Reduces operational fragmentation across hybrid environments

Cloudera Object Store (Apache Ozone)

• Enhanced metadata handling mechanisms
• Improved cluster coordination efficiency
• Stronger diagnostics tooling for better cluster health visibility

Security & Infrastructure

• 90+ Critical/High CVEs resolved
• IPv6 client support: Hue (Data Explorer), Kafka, Phoenix, Kudu, Hive, ZooKeeper, HBase, Impala
• Integrated rebase to the latest open-source components
• Strengthened security foundation for AI workloads

---

3. Per-Component Detail

Apache Iceberg

• Expanded Iceberg v2 capabilities
• New branching / tagging support
• Snapshot expiration for storage management
• Copy on Write support
• Iceberg REST Catalog API integrated with the Hive Metastore (HMS)

Apache Impala

• Encryption applied to intermediate result caching
• Lazy materialization accelerates Parquet scans
• Hierarchical event handling improves catalog quality
• OpenTelemetry integration — better observability
• Query Profile now exposes Iceberg diagnostic metrics
• AES encrypt/decrypt function support
• Authentication support for on-premises S3-compatible object storage
• ARM-based processor support

Apache Hive

• Major Iceberg v2 work reinforced:
  • Branching / tagging
  • Snapshot expiration
  • TRUNCATE PARTITION
  • INSERT INTO / INSERT OVERWRITE PARTITION
  • DROP PARTITION
  • Improved compaction behavior
• CBO improvements that lift CTE (common table expression) performance
• Runs on ARM architecture hosts
• OpenTelemetry integration for improved observability

Apache Kudu

• ARM processor support
• New Array data type
• Flink-based real-time replication tool
• Simplified Python integration
• Configuration improvements increase cluster density
• Better memory tracking reduces OOM errors

Apache Atlas

• Full replacement of the UI with a ReactJS-based one (previously BackboneJS)
• Simpler and more stable UX
• Technical preview: auto-purge of deleted entities for better metadata performance

Apache Ranger

• Ranger RAZ now supports S3A-compatible object storage (via on-prem ID Broker)
• Consistent fine-grained security across on-premises and cloud

Apache Phoenix

• High Availability (HA) configuration support

Apache Solr

• ARM architecture support (Data Hub)
• Updated to HBase Indexer 2.6.3

Component Version Matrix

---

4. Replication Manager Enhancements

These changes are worth grouping under the hybrid data governance lens.

• Iceberg replication — cross-AWS-region support
• Ozone replication — on-premises object storage replication
• Atlas replication — Hive external tables, Iceberg metadata
• Ranger replication — policy consistency between on-prem ↔ cloud
• Strengthened FIPS 140-2 compliance

---

5. Upgrade Paths

Versions Eligible for Direct In-Place Upgrade

The following versions can perform a one-step direct upgrade to 7.3.2:

• 7.1.7 SP3
• 7.1.9 SP1
• 7.3.1
• 7.2.18

Recommendation by Current Version

---

6. Environment Compatibility — Discontinued

These environments are no longer supported on 7.3.2 / Cloudera Manager 7.13.2. Verify before upgrading.

Databases

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

Operating Systems

• SLES 15 SP4
• Ubuntu 20.04

Python

• 3.8 / 3.9 / 3.10 — only 3.11 is supported

JDK

• JDK 8 / JDK 11 (across Azul, OpenJDK, and Oracle distributions) — only JDK 17 is supported

---

7. Newly Supported Environments

Operating Systems

• RHEL 9.6
• Rocky Linux 9.6
• Ubuntu 24.04
• SLES 15 SP6

Databases

• MariaDB 11.4

---

8. Compatibility with Cloudera Data Services (Caution)

If you are running Cloudera Data Services 1.5.5 (or 1.5.5 SP1 / 1.5.5 SP2), including Cloudera AI, on the same cluster, do not install or upgrade to Cloudera Base on-premises 7.3.2.

The compatible combinations are:

• Cloudera Data Services on-premises 1.5.5 SP1 (excluding Cloudera AI)
• Cloudera Data Services on-premises 1.5.5 SP2 (excluding Cloudera AI)

Plan upgrade timing alongside the Data Services version matrix to stay safe.

---

9. Other Notable Changes

Cloudera Data Explorer

• A rebrand of the existing Hue. Positioned as the first step in a series of UI and feature improvements.

Automated Data Lifecycle Management (Ozone, Technical Preview)

• Automatic transition of 3-way replicated blocks to Erasure Coding
• Expected up to 50% reduction in physical storage usage

---

10. Who Should Move to 7.3.2 Now

The cases that capture the most value:

• Organizations still on 7.1.7 / 7.1.9 / 7.3.1 / 7.2.18 — the cost and risk of a direct in-place upgrade are lowest right now while the path is open
• Organizations committing to a hybrid cloud strategy — Cloud Bursting, Data Sharing, and Replication Manager arrive together
• Organizations looking to lower Iceberg operational cost — the Lakehouse Optimizer is the largest ROI lever
• Organizations stuck on legacy OSes / JDK 8 or 11 — a trigger to migrate to the modern JDK 17 and current RHEL/Ubuntu/SLES stack

Conversely, if you are running Data Services 1.5.5-series including Cloudera AI, validate the compatibility matrix before adopting 7.3.2.

---

Summary

Cloudera Base on-premises 7.3.2 is not just a minor version bump — it's designed as the LTS terminus you can ride through 2032.

• Lakehouse Optimizer · Data Sharing · Cloud Bursting — the three pillars of a hybrid data platform
• Iceberg v2 reinforcement · OpenTelemetry · ARM support — answer modern data/AI workloads
• JDK 17 standardization · IPv6 · 90+ CVE fixes — security and infrastructure modernization
• Clear upgrade paths — single-step entry from 7.1.7 SP3, 7.1.9 SP1, 7.3.1, and 7.2.18

The detailed announcement is available in Cloudera's official Base on-premises 7.3.2 documentation.