Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/v3/core/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -339,10 +339,8 @@ The following figure illustrates the first part of the terminology:
Upon retrieval, the original keys and bytes are restored within the
transformer. Any number of storage transformers can be registered and
stacked. In contrast to codecs, storage transformers can act on the
complete array, rather than individual chunks. See the
`storage transformers details`_ below.

.. _`storage transformers details`: #storage-transformers-1
complete array, rather than individual chunks. See
:ref:`storage transformers details <storage-transformers-details>` below.

The following figure illustrates the codec, store and storage transformer
terminology for a use case of reading from an array:
Expand Down Expand Up @@ -1459,14 +1457,16 @@ Let "+" be the string concatenation operator.
For listable stores, ``list_dir(parent(P))`` can be an alternative.


.. _storage-transformers-details:

Storage transformers
====================

A Zarr storage transformer modifies a request to read or write data before passing
that request to the following transformer or store.
The stored transformed data is restored to its original state whenever data is requested
by the Array. Storage transformers can be configured per array via the
`storage_transformers <storage_transformers_>`_ name in the `array metadata`_. Storage transformers which do
:ref:`storage_transformers <array-metadata-storage-transformers>` name in the `array metadata`_. Storage transformers which do
not change the storage layout (e.g. for caching) may be specified at runtime without
adding them to the array metadata.

Expand Down