Client Interfaces

This section documents the interfaces that clients can use to communicate with Ozone.

📄️ Ozone Shell

Ozone shell is the primary interface to interact with Ozone from the command line. Behind the scenes it uses the Java API.

📄️ ofs

The Hadoop compatible file system interface allows storage backends like Ozone to be easily integrated into Hadoop eco-system. Ozone file system is a Hadoop compatible file system.

🗃️ S3 API

2 items

📄️ s3a

Ozone exposes an S3-compatible REST interface via the S3 Gateway. Hadoop's S3A filesystem (s3a://) is a cloud connector that translates the AWS S3 API into a Hadoop-compatible file system interface. Hadoop-style data analytics tools such as Hive, Impala, and Spark can access Ozone's S3 interface using the Hadoop S3A connector, so you can use Ozone buckets from existing Hadoop ecosystem tools without application changes.

📄️ HttpFS Gateway

Ozone HttpFS can be used to integrate Ozone with other tools via REST API.

📄️ Java Client API

The Apache Ozone Java Client API provides programmatic access to Ozone storage.

📄️ Accessing Apache Ozone from Python

Apache Ozone project itself does not provide Python client libraries.

📄️ CSI Protocol

Ozone CSI support is still in alpha phase and buckets can be mounted only via 3rd party S3 compatible Fuse implementation (like Goofys).

📄️ Native C/C++ Client Access to Ozone

Components Summary