Skip to content

Conversation

@LDeakin
Copy link
Member

@LDeakin LDeakin commented Jan 9, 2026

No description provided.

@LDeakin LDeakin requested a review from ilan-gold January 9, 2026 06:23
@LDeakin LDeakin added the enhancement New feature or request label Jan 9, 2026
@LDeakin LDeakin linked an issue Jan 9, 2026 that may be closed by this pull request
5 tasks
@LDeakin LDeakin merged commit 90037e2 into main Jan 9, 2026
17 checks passed
@LDeakin LDeakin deleted the ld/obstore branch January 9, 2026 11:30
Comment on lines +63 to +64
let object_store: Arc<dyn zarrs_object_store::object_store::ObjectStore> =
external_object_store.into_dyn();

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be clear here, what this is doing is taking the configuration from an existing obstore store and recreating a new store with the same parameters in the currently-linked object_store crate. So that means any connection pooling will not be shared between the user's input obstore instance and the instance you use to make your own fetches.

That's why the original idea in pyo3-object_store was that downstream crates would re-export the obstore store creation API, so that there wouldn't be any of this "dynamic linking" across crates. Since we don't have real dynamic linking, in effect we have to re-create all the necessary resources in the target pyo3 module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build Out Store Offerings

4 participants