Client-server compatibility

Client-server API compatibility in Cloudera Enterprise Data Platform ensures seamless interactions between components, even with updates to the client or the server.

Cloudera Enterprise Data Platform involves multiple layers for which API compatibility is critical. Each component in the Cloudera stack follows its own way of exchanging data using the API compatibility touchpoints, and the coverage is only being enhanced for the compatibility options.

Multiple Cloudera Runtime releases complement each other to maintain consistent API interactions.

The following table lists the supported Cloudera Runtime releases that are forward- and backward-compatible:

Table 1. Client-Server compatibility
Client	Server
7.3.2.0	7.3.2.0
7.3.1.500	7.3.2.0
CDH: 7.3.1.500-176	7.3.2.0
7.1.9.1063 and 7.1.9.1067 (Atlas, Hive, and Impala)	7.3.2.0
7.2.18.500	7.3.2.0
CDH: 7.2.18.500-67	7.3.2.0
7.2.17.1200	7.3.2.0
7.2.18.900-29	7.3.2.0
7.1.7.3023 (Hive, Ranger, Atlas, and Impala)	7.3.2.0
7.3.2.0	7.3.1.500/400
7.3.2.0	7.2.18.500, 7.2.18.900, and 7.2.18.1110
7.3.2.0	7.2.17.1200
7.3.2.0	7.1.9.1063 and 7.1.9.1067 (Atlas, Hive, and Impala)
7.3.2.0	7.1.7.3023 (Hive, Ranger, Atlas, and Impala)

For more information about each of these releases, refer to the Cloudera Product documentation.

Supported Cloudera Runtime components

Runtime components that are compatible with the categorised touchpoints.

The following table lists the Runtime components that are associated with the respective touchpoints for which the APIs are forward / backwards compatible between Cloudera Runtime releases.

important

HDFS ACLs are a core filesystem feature implemented inside the NameNode and permission model, affecting how access checks are performed at runtime. While ACL operations are exposed through multiple interfaces (Java API, CLI, WebHDFS), the compatibility concern is primarily about internal permission semantics and enforcement behavior.
Ozone S3 acts as a full-fledged S3-compatible service layer that enables external clients (like AWS SDKs or S3 tools) to communicate with Ozone storage. Ozone's S3 Gateway enables integration with a wide range of cloud-native and analytics applications.
Ozone HTTPFS provides a REST interface to perform filesystem operations over HTTP, similar to WebHDFS. Ozone HTTPFS is essentially an API gateway that exposes filesystem functionality, without introducing a new protocol or ecosystem. Ozone HTTPFS is categorized under the REST / Thrift APIs category.

Table 2. Supported Runtime compatibility
Runtime component	REST / Thrift APIs	Client Libraries and SDKs	Client-Server Interaction (Atlas / Ranger / Data Hubs / Data Services)	Command-Line Interface
Atlas	Yes	Yes	Yes	N/A
Ranger	Yes	Yes	Yes	N/A
Ranger KMS	Yes	Yes	Yes	N/A
RAZ	Yes	Yes	Yes	N/A
Knox	Yes	Yes	Yes	N/A
HBase	N/A	Yes	N/A	Yes
HDFS	Yes	Yes	N/A	Yes
Phoenix	Yes	N/A	N/A	N/A
Ozone	Yes	Yes	Yes	Yes
Hive	Yes	Yes	N/A	Yes
Impala	Yes	Yes	Yes	Yes
Livy	Yes	N/A	N/A	N/A
Spark	Yes	Yes	Yes	Yes