You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zarr-Python 2's consolidate_metadata included a path argument. However, regardless of the value provided to path, the .zmetadata JSON object was always placed at the root of the Store. This behavior changed in Zarr-Python 3. Was this intentional and if so, is it really what we want?
I know @TomAugspurger gave this some thought when implementing consolidated metadata for zarr-python 3. So perhaps we just need to document that this change was indeed intentional?
Is there actually a use case for consolidated metadata that is not at the root? It seems to me that every time you want consolidated metadata you would like to have it for the whole store, i.e. at the root.
I would need to check the v2 implementation, but my recollection is that it didn't create consolidated metadata for the entire store, unless you called it with the root group. If you do zarr.convenience.consolidate_metadata(store, path="path/to/group"), that would write the consolidated metadata for just that group (and its children) at the root of the store. If you do zarr.convenience.consolidate_metadata(store, path="path/to/another-group"), it would overwrite the metadata at the root of the store (https://zarr.readthedocs.io/en/v2.18.4/api/convenience.html#zarr.convenience.consolidate_metadata).
So if you want to consolidate for the entire store in v3, you can still have that with zarr.consoildate_metadata(store) (no path / group).
In xarray's case, I guess the hope / expectation is that you can consolidate a specific group and have it show up in the root of the store?
Zarr version
v3.0.5
Numcodecs version
v0.15.1
Python Version
Python 3.11
Operating System
Mac
Installation
conda/pip
Description
Zarr-Python 2's
consolidate_metadata
included apath
argument. However, regardless of the value provided topath
, the.zmetadata
JSON object was always placed at the root of the Store. This behavior changed in Zarr-Python 3. Was this intentional and if so, is it really what we want?I know @TomAugspurger gave this some thought when implementing consolidated metadata for zarr-python 3. So perhaps we just need to document that this change was indeed intentional?
Steps to reproduce
Additional output
xref: pydata/xarray#10020
The text was updated successfully, but these errors were encountered: