zarr_metadata.v3.chunk_key_encoding
zarr_metadata.v3.chunk_key_encoding ¶
Zarr v3 chunk key encoding metadata types.
Each chunk key encoding lives in its own submodule:
default-- v3 default encoding (/-separated)v2-- v2-compatibility encoding (.-separated by default)
Both are defined by the v3 core spec: https://github.com/zarr-developers/zarr-specs/blob/fc7dd9c9beb5a50b87f9b08b00bf50fc0048482f/docs/v3/chunk-key-encodings/default/index.rst https://github.com/zarr-developers/zarr-specs/blob/fc7dd9c9beb5a50b87f9b08b00bf50fc0048482f/docs/v3/chunk-key-encodings/v2/index.rst
The <X>ChunkKeyEncodingMetadata aliases re-exported here are the canonical
type for each encoding's permitted JSON shapes. For the underlying
<X>ChunkKeyEncodingObject, <X>ChunkKeyEncodingConfiguration, etc., import
directly from the leaf submodule.
See https://zarr-specs.readthedocs.io/en/latest/v3/core/index.html#chunk-key-encoding
zarr_metadata.v3.chunk_key_encoding.default ¶
Default chunk key encoding (Zarr v3 core spec).
The chunk key for a chunk with grid index (k, j, i, ...) is formed
by appending c<sep>k<sep>j<sep>i... (where <sep> is separator).
See https://zarr-specs.readthedocs.io/en/latest/v3/core/index.html#chunk-key-encoding
DEFAULT_CHUNK_KEY_ENCODING_NAME
module-attribute
¶
DEFAULT_CHUNK_KEY_ENCODING_NAME: Final = 'default'
The name field value of the default chunk key encoding.
DEFAULT_CHUNK_KEY_ENCODING_SEPARATOR
module-attribute
¶
DEFAULT_CHUNK_KEY_ENCODING_SEPARATOR: Final = ('/', '.')
Tuple of permitted values for the separator field of the default chunk key encoding.
DefaultChunkKeyEncodingMetadata
module-attribute
¶
DefaultChunkKeyEncodingMetadata = (
DefaultChunkKeyEncodingObject
| DefaultChunkKeyEncodingName
)
Permitted JSON shapes for the default chunk-key encoding metadata.
The configuration has no required keys (separator defaults to "/"),
so the short-hand-name form is permitted in addition to the object form.
DefaultChunkKeyEncodingName
module-attribute
¶
DefaultChunkKeyEncodingName = Literal['default']
Literal type of the name field of the default chunk key encoding.
DefaultChunkKeyEncodingSeparator
module-attribute
¶
DefaultChunkKeyEncodingSeparator = Literal['/', '.']
Literal type of permitted separator values for the default chunk key encoding.
Defaults to "/" if absent.
__all__
module-attribute
¶
__all__ = [
"DEFAULT_CHUNK_KEY_ENCODING_NAME",
"DEFAULT_CHUNK_KEY_ENCODING_SEPARATOR",
"DefaultChunkKeyEncoding",
"DefaultChunkKeyEncodingConfiguration",
"DefaultChunkKeyEncodingMetadata",
"DefaultChunkKeyEncodingName",
"DefaultChunkKeyEncodingObject",
"DefaultChunkKeyEncodingOptions",
"DefaultChunkKeyEncodingSeparator",
]
DefaultChunkKeyEncoding
dataclass
¶
Bases: ChunkKeyEncodingEntity
The default chunk key encoding, coerced from its metadata.
Source code in src/zarr_metadata/v3/chunk_key_encoding/default.py
configuration
instance-attribute
¶
configuration: DefaultChunkKeyEncodingOptions
The record of this entity's members.
An entity with members narrows it to its own record, configuration:
GzipOptions, its one positional argument. An entity of a bare name
defaults it to the empty record -- configuration: Configuration =
field(default_factory=Configuration) -- so that Crc32cCodec()
builds; coerce passes the record either way.
identifier
class-attribute
¶
identifier: str = DEFAULT_CHUNK_KEY_ENCODING_NAME
The name this entity is registered under.
Usually the name the metadata carries. The raw-bytes data types are
the exception: every r<N> spelling is one family, so the family gets
an invented identifier that no real name can collide with.
__post_init__ ¶
Refuse a record that is not this entity's own, then the first problem the rules find.
The runtime half of the entity's type, as the record's constructor
is of the record's: GzipCodec(BloscOptions(...)) and a family
member carrying a name that is not a string are refused before
any rule reads them. Then BloscCodec(BloscOptions(clevel=99))
raises on the first problem the rules yield.
Source code in src/zarr_metadata/v3/_entity.py
accepts
classmethod
¶
Whether name denotes this entity.
Constant for all but the raw-bytes family, where one class covers
every r<N>.
canonical ¶
canonical() -> Self
This entity in the simplest form that means the same thing.
A transformation, asked for by canonicalize_array_metadata_v3
and by nothing else. to_json does not apply it, because writing
a document back is not the same as asking for it to be rewritten:
a reader that reads and writes should not change bytes it was not
asked to change.
The default is the entity itself. Override it where two spellings
of the entity's members mean the same -- a rectilinear
dimension's run-length encoding, a typesize that noshuffle
ignores -- and, in an entity that contains entities, to put those
in canonical form: self.with_configuration(inner=self.inner.canonical()).
Source code in src/zarr_metadata/v3/_entity.py
coerce
classmethod
¶
value as this entity, or the reasons it is not one: the class's validation routine.
resolve relates a field's name to this class and hands it the
field, refined JSON with arrays as tuples, which is what value
is; this is what the class does with it. The configuration is
parsed against the record the configuration field names,
member by member; a member holding another entity is read in
context, the scope this reading is happening in. An optional
member the document left out is UNSET in the record, so no
field's default decides what a document said. The entity is
built only when every member of its own read -- its rules are
written over a whole configuration -- and handed back only when
everything inside it read too.
The envelope is the field's, not the class's, and resolve
judges it: a stray member or a must_understand of false is
not reported here. Called on a class no scope has registered,
this runs with none of registration's refusals having happened.
Source code in src/zarr_metadata/v3/_entity.py
create_unchecked
classmethod
¶
This entity with these fields, built without the constructor's checks.
The one way around them, for a caller that has just made them:
coerce, which type-checked the record and ran the rules before
building. Every field is given -- the record, and the carried
name for a family -- since nothing here applies a default.
Anything that has not checked goes through the constructor.
Source code in src/zarr_metadata/v3/_entity.py
name_problems
classmethod
¶
name_problems(name: str) -> Iterator[ValidationProblem]
Why name, which accepts claimed, is not a well-formed name of this family.
For a family, whose names carry data -- r<N> -- and which claims
a malformed member so that it is reported rather than waved
through as an unknown extension. Locations are relative to the
entity: (). Default: none, for an entity of one name.
Source code in src/zarr_metadata/v3/_entity.py
to_json ¶
to_json() -> ZarrV3MetadataFieldJSON
This entity as a document would write it.
Written from the configuration record by the same declaration
coerce reads it by, each member by the writer its annotation
implies: the bare name when every member it holds is absent, the
object otherwise, a contained entity through its own to_json,
a JSON-valued member copied so the document is not a handle on
the entity. Faithful to every member: read a document, write it
back, and those come out as they went in. The envelope is
written the entity's way -- the bare name when nothing is
configured, the object otherwise, no must_understand, which
means what absence means -- because an entity alone has no
document to be faithful to; ArrayDocumentV3.to_json puts back
the spelling the document used. Ask canonical first if you
want the simplest equivalent spelling.
An entity whose JSON is not its fields overrides this; none in the package does.
Source code in src/zarr_metadata/v3/_entity.py
with_configuration ¶
This entity with these configuration members changed.
codec.with_configuration(typesize=UNSET) is the record rebuilt
through its constructor, which refuses a member of the wrong
type, and the entity rebuilt through its own, which refuses a
value the rules disallow -- the same checks as any construction,
since pyright cannot see the members through **changes. A
name that is not a member is refused the way replace refuses
it.
Source code in src/zarr_metadata/v3/_entity.py
DefaultChunkKeyEncodingConfiguration ¶
Bases: TypedDict
Configuration for the default chunk key encoding.
separator is optional and defaults to "/" per spec.
https://github.com/zarr-developers/zarr-specs/blob/fc7dd9c9beb5a50b87f9b08b00bf50fc0048482f/docs/v3/chunk-key-encodings/default/index.rst#L27-L29
Source code in src/zarr_metadata/v3/chunk_key_encoding/default.py
DefaultChunkKeyEncodingObject ¶
Bases: TypedDict
Default chunk key encoding metadata in object form.
Source code in src/zarr_metadata/v3/chunk_key_encoding/default.py
configuration
instance-attribute
¶
configuration: NotRequired[
DefaultChunkKeyEncodingConfiguration
]
DefaultChunkKeyEncodingOptions
dataclass
¶
Bases: Configuration
What the default encoding is configured with.
Source code in src/zarr_metadata/v3/chunk_key_encoding/default.py
separator
class-attribute
instance-attribute
¶
separator: DefaultChunkKeyEncodingSeparator | UNSET = UNSET
__post_init__ ¶
Refuse every member of the wrong type, so GzipOptions(level="high") raises.
create_unchecked
classmethod
¶
This record with these members, built without the constructor's check.
The one way around the check, for a caller that has just made
it: the parser, which type-checked every member against the same
annotations before building the record. Every field is given --
the parser gives an absent optional member as UNSET -- since
nothing here applies a default. Anything that has not checked
the members goes through the constructor.
Source code in src/zarr_metadata/v3/_entity.py
problems ¶
problems() -> Iterator[ValidationProblem]
zarr_metadata.v3.chunk_key_encoding.v2 ¶
v2-compatibility chunk key encoding (Zarr v3 core spec).
Intended only to allow existing v2 arrays to be converted to v3 without having to rename chunks. Not recommended for new arrays.
Naming note: these are Zarr v3 types. The leading V2 in
V2ChunkKeyEncodingMetadata (and friends) is the encoding's registered
entity name ("v2"), not the format-version marker that ZarrV2...
names carry — this package's version-prefixed names always spell it
ZarrV2 / ZarrV3.
See https://zarr-specs.readthedocs.io/en/latest/v3/core/index.html#chunk-key-encoding
V2ChunkKeyEncodingMetadata
module-attribute
¶
V2ChunkKeyEncodingMetadata = (
V2ChunkKeyEncodingObject | V2ChunkKeyEncodingName
)
Permitted JSON shapes for the v2-compatibility chunk-key encoding metadata.
The configuration has no required keys (separator defaults to "."),
so the short-hand-name form is permitted in addition to the object form.
V2ChunkKeyEncodingName
module-attribute
¶
V2ChunkKeyEncodingName = Literal['v2']
Literal type of the name field of the v2 chunk key encoding.
V2ChunkKeyEncodingSeparator
module-attribute
¶
V2ChunkKeyEncodingSeparator = Literal['/', '.']
Literal type of permitted separator values for the v2 chunk key encoding.
Defaults to "." if absent.
V2_CHUNK_KEY_ENCODING_NAME
module-attribute
¶
V2_CHUNK_KEY_ENCODING_NAME: Final = 'v2'
The name field value of the v2 chunk key encoding.
V2_CHUNK_KEY_ENCODING_SEPARATOR
module-attribute
¶
V2_CHUNK_KEY_ENCODING_SEPARATOR: Final = ('/', '.')
Tuple of permitted values for the separator field of the v2 chunk key encoding.
__all__
module-attribute
¶
__all__ = [
"V2_CHUNK_KEY_ENCODING_NAME",
"V2_CHUNK_KEY_ENCODING_SEPARATOR",
"V2ChunkKeyEncoding",
"V2ChunkKeyEncodingConfiguration",
"V2ChunkKeyEncodingMetadata",
"V2ChunkKeyEncodingName",
"V2ChunkKeyEncodingObject",
"V2ChunkKeyEncodingOptions",
"V2ChunkKeyEncodingSeparator",
]
V2ChunkKeyEncoding
dataclass
¶
Bases: ChunkKeyEncodingEntity
The v2 chunk key encoding, coerced from its metadata.
Source code in src/zarr_metadata/v3/chunk_key_encoding/v2.py
configuration
instance-attribute
¶
configuration: V2ChunkKeyEncodingOptions
The record of this entity's members.
An entity with members narrows it to its own record, configuration:
GzipOptions, its one positional argument. An entity of a bare name
defaults it to the empty record -- configuration: Configuration =
field(default_factory=Configuration) -- so that Crc32cCodec()
builds; coerce passes the record either way.
identifier
class-attribute
¶
identifier: str = V2_CHUNK_KEY_ENCODING_NAME
The name this entity is registered under.
Usually the name the metadata carries. The raw-bytes data types are
the exception: every r<N> spelling is one family, so the family gets
an invented identifier that no real name can collide with.
__post_init__ ¶
Refuse a record that is not this entity's own, then the first problem the rules find.
The runtime half of the entity's type, as the record's constructor
is of the record's: GzipCodec(BloscOptions(...)) and a family
member carrying a name that is not a string are refused before
any rule reads them. Then BloscCodec(BloscOptions(clevel=99))
raises on the first problem the rules yield.
Source code in src/zarr_metadata/v3/_entity.py
accepts
classmethod
¶
Whether name denotes this entity.
Constant for all but the raw-bytes family, where one class covers
every r<N>.
canonical ¶
canonical() -> Self
This entity in the simplest form that means the same thing.
A transformation, asked for by canonicalize_array_metadata_v3
and by nothing else. to_json does not apply it, because writing
a document back is not the same as asking for it to be rewritten:
a reader that reads and writes should not change bytes it was not
asked to change.
The default is the entity itself. Override it where two spellings
of the entity's members mean the same -- a rectilinear
dimension's run-length encoding, a typesize that noshuffle
ignores -- and, in an entity that contains entities, to put those
in canonical form: self.with_configuration(inner=self.inner.canonical()).
Source code in src/zarr_metadata/v3/_entity.py
coerce
classmethod
¶
value as this entity, or the reasons it is not one: the class's validation routine.
resolve relates a field's name to this class and hands it the
field, refined JSON with arrays as tuples, which is what value
is; this is what the class does with it. The configuration is
parsed against the record the configuration field names,
member by member; a member holding another entity is read in
context, the scope this reading is happening in. An optional
member the document left out is UNSET in the record, so no
field's default decides what a document said. The entity is
built only when every member of its own read -- its rules are
written over a whole configuration -- and handed back only when
everything inside it read too.
The envelope is the field's, not the class's, and resolve
judges it: a stray member or a must_understand of false is
not reported here. Called on a class no scope has registered,
this runs with none of registration's refusals having happened.
Source code in src/zarr_metadata/v3/_entity.py
create_unchecked
classmethod
¶
This entity with these fields, built without the constructor's checks.
The one way around them, for a caller that has just made them:
coerce, which type-checked the record and ran the rules before
building. Every field is given -- the record, and the carried
name for a family -- since nothing here applies a default.
Anything that has not checked goes through the constructor.
Source code in src/zarr_metadata/v3/_entity.py
name_problems
classmethod
¶
name_problems(name: str) -> Iterator[ValidationProblem]
Why name, which accepts claimed, is not a well-formed name of this family.
For a family, whose names carry data -- r<N> -- and which claims
a malformed member so that it is reported rather than waved
through as an unknown extension. Locations are relative to the
entity: (). Default: none, for an entity of one name.
Source code in src/zarr_metadata/v3/_entity.py
to_json ¶
to_json() -> ZarrV3MetadataFieldJSON
This entity as a document would write it.
Written from the configuration record by the same declaration
coerce reads it by, each member by the writer its annotation
implies: the bare name when every member it holds is absent, the
object otherwise, a contained entity through its own to_json,
a JSON-valued member copied so the document is not a handle on
the entity. Faithful to every member: read a document, write it
back, and those come out as they went in. The envelope is
written the entity's way -- the bare name when nothing is
configured, the object otherwise, no must_understand, which
means what absence means -- because an entity alone has no
document to be faithful to; ArrayDocumentV3.to_json puts back
the spelling the document used. Ask canonical first if you
want the simplest equivalent spelling.
An entity whose JSON is not its fields overrides this; none in the package does.
Source code in src/zarr_metadata/v3/_entity.py
with_configuration ¶
This entity with these configuration members changed.
codec.with_configuration(typesize=UNSET) is the record rebuilt
through its constructor, which refuses a member of the wrong
type, and the entity rebuilt through its own, which refuses a
value the rules disallow -- the same checks as any construction,
since pyright cannot see the members through **changes. A
name that is not a member is refused the way replace refuses
it.
Source code in src/zarr_metadata/v3/_entity.py
V2ChunkKeyEncodingConfiguration ¶
Bases: TypedDict
Configuration for the v2 chunk key encoding.
separator is optional and defaults to "." per spec.
https://github.com/zarr-developers/zarr-specs/blob/fc7dd9c9beb5a50b87f9b08b00bf50fc0048482f/docs/v3/chunk-key-encodings/v2/index.rst#L27-L29
Source code in src/zarr_metadata/v3/chunk_key_encoding/v2.py
V2ChunkKeyEncodingObject ¶
Bases: TypedDict
v2-compatibility chunk key encoding metadata in object form.
Source code in src/zarr_metadata/v3/chunk_key_encoding/v2.py
V2ChunkKeyEncodingOptions
dataclass
¶
Bases: Configuration
What the v2 encoding is configured with.
Source code in src/zarr_metadata/v3/chunk_key_encoding/v2.py
separator
class-attribute
instance-attribute
¶
separator: V2ChunkKeyEncodingSeparator | UNSET = UNSET
__post_init__ ¶
Refuse every member of the wrong type, so GzipOptions(level="high") raises.
create_unchecked
classmethod
¶
This record with these members, built without the constructor's check.
The one way around the check, for a caller that has just made
it: the parser, which type-checked every member against the same
annotations before building the record. Every field is given --
the parser gives an absent optional member as UNSET -- since
nothing here applies a default. Anything that has not checked
the members goes through the constructor.
Source code in src/zarr_metadata/v3/_entity.py
problems ¶
problems() -> Iterator[ValidationProblem]