-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide more informative error messages for obs.put_async
with incorrect "mode"
#281
Comments
Hmm I'm not sure what you're seeing. Any capitalization should work: Lines 31 to 34 in 28ba07a
|
The underlying obstore/pyo3-object_store/src/error.rs Lines 136 to 138 in 28ba07a
So what you're probably seeing is an error thrown by object_store
|
Your error is coming from here: https://github.com/apache/arrow-rs/blob/b666e424e8f395e9a9bb9950ffab1f968312e103/object_store/src/aws/mod.rs#L172 This is because S3 just added conditional puts recently, and it's not yet the default behavior. For now, I think you have to explicitly opt-in when you create the S3Store You need to set |
https://github.com/maxrjones/zarr-obstore-performance/blob/main/notebooks/zarr-obstore-write.ipynb shows the error. I wasn't able to quickly make a simpler example with just Zarr (rather than xarray + zarr), I guess Zarr's I won't have time for more debugging until Friday, but I could rerun the test notebook with any changes to see if it works. |
We noticed in the Obstore <-> Zarr-Python integration that using
obs.put_async(self.store, key, buf, mode="create")
raises aNotImplementedError
. A different error type would make it more clear to the user that"create"
needs to be"Create"
(notice capitalization) (e.g., kylebarron/zarr-python#16).The text was updated successfully, but these errors were encountered: