-
Notifications
You must be signed in to change notification settings - Fork 27
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
ManifestArray should use zarr-python's ArrayV3Metadata #424
Comments
Splitting out refactoring
However I don't think you should try to support both at once inside Instead, you should change def zarray_to_v3metadata(zarray: ZArray) -> ArrayV3Metadata:
... and calling that in the readers just before they create a
If you wanted to avoid changing test assertions (that would now have to check |
That makes sense! Thanks @TomNicholas |
FYI I'm working on this in manifest-arrays-use-arrayv3metadata, not quite ready for a draft PR as I'm still working through the implementation and tests. Hoping to finish tomorrow 🤞🏽 |
Amazing! FYI @TomNicholas this is also required for the Manifest/Functional Store idea from here and here. The Store can easily handle when key= |
I have opened a draft PR: #429 but as you can see in the description and failing tests there is still a bit of work to do. |
En route to replacing
ZArray
custom class with zarr-python'sArrayV3Metadata
, we first need to support ManifestArrays usingArrayV3Metadata
.In order to achieve #411 in an incremental way, my proposal is to first support
ArrayV3Metadata
as well asZArray
in ManifestArray's, so that we can then incrementally refactor the readers and writers to implement or use ManifestArray's usingArrayV3Metadata
while still having passing tests. Once all readers and writers using ManifestArrays are refactored, we can remove the customZArray
class.As suggested in #411, this will include renaming the ManifestArray
zarray
property tometadata
.See also #423 for a reference on how codec pipelines may be handled.
Thoughts welcome, cc @mpiannucci @TomNicholas
The text was updated successfully, but these errors were encountered: