-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Allow chunk_store argument when opening Zarr datasets #3804
Conversation
This PR is motivated by the work described in this Medium blog post |
Fantastic, thanks @ajelenak so much for this contribution! Two items come to mind:
|
@rabernat Added a test that uses an actual Zarr store. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the update.
The new test is unfortunately failing with the error
E TypeError: open() got multiple values for keyword argument 'chunk_store'
Could you look into this?
As noted in comment below, this test also makes me wonder whether we want a chunk_store
argument in to_zarr
as well. It might make sense to do them both as part of this PR.
# Conflicts: # xarray/tests/test_backends.py
Sorry for letting this hang so long. Now that zarr-developers/zarr-python#557 has been merged and zarr 2.4.0 has been released, we should be able to finish this off. The easiest thing would be to just require zarr > 2.4.0. However, we currently don't require zarr at all...it's an optional dependency. The code in this PR will fail for older versions of zarr. What's the best way to handle this? Having a bunch of internal checks for zarr versions feels clunky, but we've done it before. |
It'd be nice to add some documentation to https://xarray.pydata.org/en/stable/io.html but that can happen in a future PR. |
@dcherian , are we just waiting for one more "+1" here, or are the failing checks related to this PR? |
* upstream/master: (36 commits) enable fail_on_warning for RTD (#4269) update the list item numbers in the release guide (#4264) remove the compatibility code in duck_array_ops.allclose_or_equiv (#4270) Un-xfail cftime plotting tests (#4272) xfail failing upstream plotting tests (#4271) Improve some error messages: apply_ufunc & set_options. (#4259) Support cupy in as_shared_dtype (#4232) Fix DataArray.copy documentation: remove confusing mention of 'dataset' (Gh3606) (#4245) Removed skipna argument from count, any, all [GH755] (#4258) Added xarrays-spatial and updated geoviews link (#4262) update docs to point to xarray-contrib and xarray-tutorial (#4252) Add release summary, some touch-ups (#4217) CFTimeIndex calendar in repr (#4092) fix the RTD timeouts (#4254) update isort CI and pre-commit hook (#4204) Add initial cupy tests (#4214) Add 0.16.0 release summary New whatsnew section Release v0.16.0 Minor reorg of whatsnew for 0.16.0 (#4216) ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this LGTM as long as tests pass.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cycled the CI to (hopefully) fix the failing test. In the meantime, two other comments popped out at me.
…hunkstore Fixed conflicts in: • xarray/core/dataset.py • xarray/tests/test_sparse.py
Is there anything else to be done in this PR, or is it ready for merge? All tests pass. |
Looks good to me. I will merge in a couple of days if no one else has any comments. |
Drumroll.... @dcherian, epic cymbal crash? |
Thanks for being patient @ajelenak I am excited to see this go in. welcome to xarray! |
Thanks @dcherian . And thanks to all who provided suggestions and comments in this PR. |
This is a simple modification to pass
chunk_store
argument to the zarr package when opening Zarr datasets.I don't think this requires any documentation changes and new tests.