Skip to content
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

Treatment of filters / compressors is not consistent with V3 "codecs" #1269

Closed
rabernat opened this issue Nov 17, 2022 · 1 comment
Closed

Comments

@rabernat
Copy link
Contributor

With zarr-developers/zarr-specs#153, the V3 spec was updated to use a single codec field in array metadata, rather than the separate filters and compressor fields. The specific text is

codecs
Specifies a list of codecs to be used for encoding and decoding chunks. The value must be an array of objects, each object containing a member with type whose value is a URI that identifies a codec and dereferences to a human-readable representation of the codec specification. The codec object may also contain a configuration object which consists of the parameter names and values as defined by the corresponding codec specification. An absent codecs member is equivalent to specifying an empty list of codecs.

AFAICT, this library (zarr-python) has not been updated to reflect this new concept. I'm opening this issue to keep track of this.

@jhamman
Copy link
Member

jhamman commented Dec 7, 2023

Closing as this is now done on the v3 branch. See #1583 for more context on the v3 effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants