Experimental chunk manifest support #79
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work in progress to enable stores that reference bytes created outside Zarr (via
virtualizarr
)Notes
python3 virtualizarr_gen.py
zarr.json
metadatacargo test chunk_manifest
TODO
virtualizarr
manifest.json
virtualizarr
should writepath
s relative to the hierarchy root. Currently they are relative to the working directory.Or is there a more general way of handling this (via metadata changes)? The store must be opened at the same location as the CWD whenvirtualize.to_zarr
was called. Can't just open a store pointing directly at the hierarchy and then open an array at the root store prefix...zarr.json
zarrs
already supports variable length chunks"0.0"
etc).chunk-manifest-json
storage transformer should not need to be aware of the chunk key encodingDefaults toConformant ZarrV3 codecs and fill values zarr-developers/VirtualiZarr#193"codecs": null,
without netCDF compression. Change toDefaults toConformant ZarrV3 codecs and fill values zarr-developers/VirtualiZarr#193"fill_value": null
. Must be set to a compatible value.zarrs