| Crates.io | zarrs_object_store |
| lib.rs | zarrs_object_store |
| version | 0.5.0 |
| created_at | 2024-09-02 10:58:29.353559+00 |
| updated_at | 2025-09-17 23:15:30.865735+00 |
| description | object_store store support for the zarrs crate |
| homepage | https://zarrs.dev |
| repository | https://github.com/zarrs/zarrs/tree/main/zarrs_object_store |
| max_upload_size | |
| id | 1360385 |
| size | 84,164 |
object_store store support for the zarrs Rust crate.
use zarrs_storage::AsyncReadableWritableListableStorage;
use zarrs_object_store::AsyncObjectStore;
let options = object_store::ClientOptions::new().with_allow_http(true);
let store = object_store::http::HttpBuilder::new()
.with_url("http://...")
.with_client_options(options)
.build()?;
let store: AsyncReadableWritableListableStorage =
Arc::new(AsyncObjectStore::new(store));
See doc/version_compatibility_matrix.md.
object_store is re-exported as a dependency of this crate, so it does not need to be specified as a direct dependency.
You can enable object_store features fs, aws, azure, gcp and http by enabling features for this crate of the same name.
However, if object_store is a direct dependency, it is necessary to ensure that the version used by this crate is compatible.
This crate can depend on a range of semver-incompatible versions of object_store, and Cargo will not automatically choose a single version of object_store that satisfies all dependencies.
Use a precise cargo update to ensure compatibility.
For example, if this crate resolves to object_store 0.11.1 and your code uses 0.10.2:
cargo update --package object_store:0.11.1 --precise 0.10.2
zarrs_object_store is licensed under either of
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.