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
{{ message }}
Repository navigation
Commit 8b7af90
Browse filesBrowse the repository at this point in the historyBrowse files
Zarr V2 uses a separate JSON document named `.zattrs` for the attributes of an array or group.
This package was inconsistent about how it modelled this fact. The array metadata document type modelled
array fields (`shape`, `dtype`, etc), which would be stored in `.zarray`, AND the `attributes` field,
which would be stored in `.zattrs`. Thus the array metadata model matched the representation
of an array that a program might use, rather than the stored layout. But the group metadata type didn't
follow this pattern -- it has no `attributes` field.
This PR addresses that inconsistency by adding an `attributes` field to `GroupMetadataV2`. That field is
not required. To model the stored representation of V2 data, this PR adds 3 new types: `ZArrayMetadata`,
`ZGroupMetadata`, and `ZAttrsMetadata`, that closely model the contents of the `.zarray`, `.zgroup`, and
`.zattrs` documents, respectively.
This change makes the V2 consolidated metadata type more accurate, as consolidated metadata for Zarr V2
is comprised of inlined metadata documents.
0 commit comments