Skip to content

Update zarr 3 codec pipeline workflow#423

Merged
TomNicholas merged 4 commits intozarr-developers:mainfrom
mpiannucci:zarr3-codec-update
Feb 10, 2025
Merged

Update zarr 3 codec pipeline workflow#423
TomNicholas merged 4 commits intozarr-developers:mainfrom
mpiannucci:zarr3-codec-update

Conversation

@mpiannucci
Copy link
Contributor

@mpiannucci mpiannucci commented Feb 4, 2025

We need to handle codecs so that they match the zarr 3 create_array api

@mpiannucci mpiannucci marked this pull request as draft February 4, 2025 15:58
@mpiannucci mpiannucci marked this pull request as ready for review February 4, 2025 16:40
@TomNicholas TomNicholas added zarr-python Relevant to zarr-python upstream v3-migration labels Feb 4, 2025
serializer = v3_codecs_to_serializer(codecs)
return ZarrV3Codecs(
filters=filters, compressors=compressors, serializer=serializer
)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm curious if we replaced the ZArray class with zarr-python's ArrayV3Metadata would there be comparable functionality to parse out the filters, compressors and serializer, so those could be passed to zarr-python's create_array (same args as require_array)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was going to do this with init_array but it requires a store path which i didnt want to deal with atm, but might be the right approach

@TomNicholas TomNicholas merged commit dd64d54 into zarr-developers:main Feb 10, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

zarr-python Relevant to zarr-python upstream

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error writing virtual dataset to icechunk

3 participants