ODH-Based Versioning in OCI Big Data Service

Beginning in September 2026, Big Data Service (BDS) uses the Oracle Distribution including Apache Hadoop (ODH) version as the primary version for cluster creation, Console display, and release documentation.

With this change, when you create or view a BDS cluster, the version shown represents the ODH platform version deployed on the cluster. For example, you might see and select versions such as ODH 2.2.3, ODH 2.2.2, or ODH 2.2.1 depending on the versions supported in the region.

The BDS version continues to be maintained by Oracle and remains available for compatibility and support.

What's Changing?

Before September 2026, cluster versions were primarily represented by the BDS version. Beginning with September 2026, Big Data Service uses the ODH version as the primary version during cluster creation and other operations.

Big Data Service maintains the following version identifiers:

• ODH version: Identifies the Oracle Distribution including Apache Hadoop platform deployed on the cluster, including Hadoop, Spark, Hive, and related services.
• BDS service version: Identifies the Big Data Service release layer associated with the cluster.

When you select an ODH version, Big Data Service provisions the supported BDS version associated with that ODH release.

Why change to ODH-based versioning?

A BDS cluster includes multiple software layers, including the OS, management software, BDS service components, and the ODH data platform. Using the ODH version as the primary version helps identify the data platform components running on the cluster.

This change helps you as follows:

• Select the intended ODH platform version when creating clusters.
• Understand which Hadoop, Spark, Hive, and related component versions are included.
• Review release documentation by the platform version deployed on the cluster.
• Continue using supported API, CLI, SDK, Terraform, and automation workflows.

What you'll see?

In the OCI Console, you'll select and view ODH versions during cluster creation.

For example:

• ODH 2.2.3
• ODH 2.2.2
• ODH 2.2.1

When you select an ODH version, OCI BDS will provision the appropriate supported BDS version associated with that ODH release. If you're using APIs or Terraform, you can use ODH version (Recommended). However, you can continue to specify supported BDS versions in existing API requests and Terraform configurations without modification.

Compatibility with API, CLI, SDK, and Terraform

For backward compatibility, API, CLI, SDK, and Terraform requests can continue to specify a supported BDS service version.

Depending on the workflow, you can create clusters by specifying:

• The ODH version only, through the OCI Console or API, CLI, SDK, and Terraform.
• The ODH version and BDS version, through API, CLI, SDK, and Terraform only.

When only the ODH version is provided, Big Data Service selects the supported BDS version associated with that ODH release. If both an ODH version and BDS service version are provided, they must be a supported combination.

Impact on Clusters Created Before September 2026

You have no action to enable these changes. The change to ODH-based versioning affects how versions are displayed and selected for cluster creation. The change doesn't affect versions of existing clusters, cluster lifecycle operations, patching behavior, or supported automation. You can identify the versions on the cluster details page in the OCI Console by checking the BDS/ODH version under the Cluster information section, or by running the following command and checking the bds-version and odh-version fields in the response:

oci bds instance get --bds-instance-id <bds_cluster_ocid>

For clusters created before this timeline, OCI Big Data Service continues to maintain the associated BDS service version, ODH version, and OS version.

The following aren't changed by ODH-based versioning:

• Running clusters
• Add node operations
• OS patching
• Cluster patching
• Data plane APIs
• Existing BDS CLI workflows
• Existing image creation workflows

Release Documentation

After September 2026, release documentation is organized around ODH versions. When a change applies to the BDS service layer and doesn't change the ODH platform version, the documentation identifies that distinction where applicable.

This helps distinguish between:

• ODH platform updates
• BDS service updates
• OS or security updates

Summary

OCI Big Data Service is adopting an ODH-centric versioning model to provide versioning that's clearer, more stable, and meaningful.

You'll select ODH versions when creating clusters, while OCI BDS continues to manage the appropriate BDS service version and image selection behind the scenes. Existing API and Terraform workflows that reference BDS versions remain fully supported for backward compatibility.