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

Handle missing chunks #32

Closed
jhamman opened this issue Mar 11, 2022 · 1 comment · Fixed by #34
Closed

Handle missing chunks #32

jhamman opened this issue Mar 11, 2022 · 1 comment · Fixed by #34

Comments

@jhamman
Copy link
Contributor

jhamman commented Mar 11, 2022

In Zarr's v2 spec, missing chunks are explicitly supported:

There is no need for all chunks to be present within an array store. If a chunk is not present then it is considered to be in an uninitialized state. An uninitialized chunk MUST be treated as if it was uniformly filled with the value of the “fill_value” field in the array metadata. If the “fill_value” field is null then the contents of the chunk are undefined.

With this in mind, this library should catch 404s and return chunk of data equal to fill_value.

cc @freeman-lab, @katamartin

@joshmoore
Copy link

Just a heads up that there are some ongoing discussions around fill_value defaults:

zarr-developers/zarr-specs#133

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

Successfully merging a pull request may close this issue.

2 participants