ODP 1.3.2.0 Roadmap
This page outlines the functional direction of ODP 1.3.2.0 and the capabilities prioritized for the release. It is a product roadmap, not a dated release calendar.
Executive Summary
ODP 1.3.2.0 extends the 1.3 platform with a stronger lakehouse foundation, broader SQL services, and a more flexible operating model across classic clusters and Kubernetes-oriented deployments.
- end-to-end Iceberg governance across Hive, Spark, Impala, Trino, Atlas, Ranger, and Polaris
- stronger interactive analytics with managed Impala and Kudu
- broader operational flexibility with OIDC, mixed JDK strategies, Ozone-oriented storage models, and Kubernetes service lifecycle management
Planned Version Trajectory
The current roadmap points to the following major version movements from 1.3.1.0 to 1.3.2.0:
| Component | 1.3.1.0 | 1.3.2.0 target | Functional impact |
|---|---|---|---|
| Hadoop core | 3.4.1 | 3.4.2 | platform maintenance and compatibility updates |
| Hive | 4.0.1 | 4.2.0 | newer Hive API surface for engines and integrations |
| Iceberg | 1.6.1 | 1.10.1 | broader table-format maturity and engine alignment |
| HBase | 2.6.1 | 2.6.4 | stability and platform alignment |
| Ozone | 2.0.0 | 2.1.0 | stronger object-store and HCFS integration |
| Ranger | 2.6.0 | 2.7.0 | expanded governance and plugin support |
| NiFi | 1.28.1 | 2.8.0 | major dataflow runtime refresh |
| Livy | 0.8.0 | 0.9.0 | updated Spark submission layer |
| Phoenix | 5.2.1 | 5.3.0 | SQL engine refresh for HBase-backed workloads |
| TEZ | 0.10.4 | 0.10.5 | execution-layer compatibility updates |
| ZooKeeper | 3.9.3 | 3.9.4 | maintenance and runtime fixes |
| Zeppelin | 0.11.1 | 0.12.0 | newer notebook runtime and integrations |
| Impala | 4.5.0 | 5.0.0 | higher-performance SQL query engine |
| Kudu | not delivered as a managed service | 1.18.1 | low-latency analytical storage for Impala workloads |
| Polaris | not present | 1.3.0 | Iceberg catalog and access-control layer |
Strategic Themes
1. Governed Lakehouse Foundation
ODP 1.3.2.0 reinforces the platform around governed Iceberg adoption:
- Hive moves to 4.2.0 and Iceberg to 1.10.1
- Atlas expands lineage and metadata coverage for Hive, Spark, Impala, and Trino
- Polaris adds a managed catalog layer with operational tooling, TLS support, and service integration
- Ranger 2.7.0 strengthens policy enforcement with Polaris integration, updated Atlas resource mapping, and OpenMetadata tag synchronization
This positions 1.3.2.0 as a governance-focused lakehouse release rather than a simple component refresh.
2. Expanded SQL and Analytics Services
ODP 1.3.2.0 broadens the analytics layer around interactive SQL and BI:
- Impala 5.0.0 becomes a managed platform service
- Kudu 1.18.1 complements Impala for low-latency analytical storage
- Trino remains part of the SQL access strategy and benefits from the broader governance integration work
- Superset extends the BI and dashboarding layer for SQL-serving environments
This gives the platform a more complete profile for batch, interactive, and self-service analytics.
3. Modernized Ambari Control Plane
Compared with the current 1.3.x baseline, the 1.3.2.0 direction expands what the management plane can operate and govern:
| Control-plane area | Current baseline | ODP 1.3.2.0 direction |
|---|---|---|
| Managed services | historical ODP footprint | adds CORE, IMPALA, KUDU, OIDC, and POLARIS |
| Storage architecture | HDFS remains the default reference model | introduces CORE as a filesystem abstraction and improves Ozone-oriented service design |
| Identity and access | Kerberos-first operating model | broadens the security model with OIDC and more flexible authentication flows |
| Java runtime strategy | single-runtime assumptions are more common | adds clearer separation between Ambari runtime requirements and component runtime requirements |
| Upgrade path | focused on the existing 1.3 service set | extends upgrade and packaging coverage for the expanded 1.3.2.0 footprint |
In practical terms, Ambari evolves from managing the existing ODP estate to orchestrating a broader and more flexible platform model.
4. Platform and Runtime Modernization
ODP 1.3.2.0 also advances the delivery baseline:
- broader JDK 21 readiness across services such as Knox, Oozie, Atlas, Spark, and Zeppelin
- stronger operating-system coverage across Ubuntu 22/24, RHEL 9, and aarch64 targets
- packaging and dependency alignment for newer runtime stacks
- safer side-by-side installation and upgrade behavior for 1.2 to 1.3 transition scenarios
5. Hybrid Kubernetes Operations
ODP 1.3.2.0 also points toward a hybrid operating model for selected analytical services on Kubernetes:
- Helm-based install, upgrade, rollback, and uninstall flows from an Ambari view
- background operations with progress tracking
- GitOps and Flux-oriented release status monitoring
- service patterns for Trino and Superset
- Ranger, LDAP, Vault, and secure keytab integration for protected deployment flows
- keytab and Kerberos helper wiring for secure chart deployment patterns
This track prepares the platform for environments where part of the analytical layer is delivered on Kubernetes while governance and operations remain centrally managed.
What This Means for Platform Teams
- a stronger governed lakehouse stack around Iceberg, Atlas, Ranger, and Polaris
- a wider SQL portfolio with Impala, Kudu, Trino, and Superset
- more flexible security and storage topologies through OIDC and CORE
- a clearer path toward hybrid operations across classic infrastructure and Kubernetes
Recommended Positioning
ODP 1.3.2.0 should be positioned as the next major functional step after 1.3.1.0: a release focused on governed lakehouse adoption, expanded analytical services, and a more modern management model.