Initial Zarr v3 Support #511
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tasansal
force-pushed
the
zarr-v3
branch
2 times, most recently
from
1eaed1f to
3159731
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactored the Zarr storage and array APIs to work with Zarr v3 engine. The datasets are still created as Zarr v2; however, I/O operations are now done with v3's new async engine.
Zarr v3 minimum Python req is 3.11 so I updated MDIO to that as well.
Good Stuff:
Limitations:
copy_storeis not implemented in v3 yet, can't copy with MDIO API.TODO:
copy_storein https://github.com/zarr-developers/zarr-pythonThis branch is based on #496