Apache OpenDAL™ object_store integration

object_store_opendal is an object_store implementation using opendal.

This crate can help you to access 30 more storage services with the same object_store API.

Useful Links

• Documentation: release | dev

Examples

opendal_store_opendal depends on the opendal crate. Please make sure to always use the latest versions of both.

latest object_store_opendal

latest opendal

1. using object_store API to access S3

Add the following dependencies to your Cargo.toml with correct version:

[dependencies]
object_store = "0.14.1"
object_store_opendal =  "xxx"   # see the latest version above
opendal = { version = "xxx", features = ["services-s3"] }  # see the latest version above

Build OpendalStore via opendal::Operator:

use std::sync::Arc;

use bytes::Bytes;
use object_store::path::Path;
use object_store::ObjectStoreExt;
use object_store_opendal::OpendalStore;
use opendal::services::S3;
use opendal::{Builder, Operator};

#[tokio::main]
async fn main() {
    let builder = S3::from_map(
        vec![
            ("access_key".to_string(), "my_access_key".to_string()),
            ("secret_key".to_string(), "my_secret_key".to_string()),
            ("endpoint".to_string(), "my_endpoint".to_string()),
            ("region".to_string(), "my_region".to_string()),
        ]
        .into_iter()
        .collect(),
    ).unwrap();

    // Create a new operator
    let operator = Operator::new(builder).unwrap();

    // Create a new object store
    let object_store = Arc::new(OpendalStore::new(operator));

    let path = Path::from("data/nested/test.txt");
    let bytes = Bytes::from_static(b"hello, world! I am nested.");

    object_store.put(&path, bytes.clone().into()).await.unwrap();

    let content = object_store
        .get(&path)
        .await
        .unwrap()
        .bytes()
        .await
        .unwrap();

    assert_eq!(content, bytes);
}

Tune vectored reads

OpendalStore coalesces ranges separated by up to 1 MiB by default, matching object_store::OBJECT_STORE_COALESCE_DEFAULT. Workloads that need to limit over-fetching can configure the gap when constructing the store:

let object_store = OpendalStore::new(operator).with_get_ranges_gap(0);

A gap of 0 disables merging ranges separated by bytes. Overlapping or adjacent ranges are still merged without over-fetching. Set an intermediate value to trade fewer backend requests for additional bytes read. A gap of 0 can be useful for HDFS scans that are sensitive to retaining large coalesced backing buffers.

WASM support

To build with wasm32-unknown-unknown target, you need to enable the send_wrapper feature:

cargo build --target wasm32-unknown-unknown --features send_wrapper

Branding

The first and most prominent mentions must use the full form: Apache OpenDAL™ of the name for any individual usage (webpage, handout, slides, etc.) Depending on the context and writing style, you should use the full form of the name sufficiently often to ensure that readers clearly understand the association of both the OpenDAL project and the OpenDAL software product to the ASF as the parent organization.

For more details, see the Apache Product Name Usage Guide.

License and Trademarks

Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0

Apache OpenDAL, OpenDAL, and Apache are either registered trademarks or trademarks of the Apache Software Foundation.