Skip to content

codecs in the config #2928

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

Open
d-v-b opened this issue Mar 24, 2025 · 0 comments
Open

codecs in the config #2928

d-v-b opened this issue Mar 24, 2025 · 0 comments

Comments

@d-v-b
Copy link
Contributor

d-v-b commented Mar 24, 2025

Our config object contains explicit parameterization of codecs, like {"name": "zstd", "configuration": {"level": 0, "checksum": False}}. I think it would be simpler to allow using just the name of the codec; the array creation routine would thus have some freedom to set codec parameters dynamically based on the user's input.

This is particularly relevant for the endian parameter of the bytes codec, which cannot be correctly specified without knowing the data type of the array. Right now our default is "little", but for single-byte dtypes this is technically wrong, and it requires modifying the default bytes codec definition on array creation time.

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

1 participant