Docs on how to write a custom reader using ManifestStore#580
Docs on how to write a custom reader using ManifestStore#580TomNicholas merged 10 commits intozarr-developers:developfrom
Conversation
TomNicholas
temporarily deployed
to
test-release
GitHub Actions
Inactive
for more information, see https://pre-commit.ci
|
|
||
| As well as being a well-defined representation of the archival data in the Zarr model, you can also read chunk data directly from the `ManifestStore` object. | ||
|
|
||
| This works because the `ManifestStore` class is an implementation of the Zarr-Python `zarr.abc.Store` interface, and uses the `obstore` package internally to actually fetch chunk data when requested. |
There was a problem hiding this comment.
This section is missing a lot of detail about the store registry and credentials, but maybe you would like to add that in a follow-up PR @maxrjones ?
There was a problem hiding this comment.
I think I over-engineered the store registry and with the proposal in #568 it could be removed.
|
@maxrjones I'm going to just merge this - we can add more material as needed later. |
That sounds good. I'd rather we use Backend for this and to keep the reader concept separate - see definitions in #568, but I'm not going to spend any effort on that hill. |
I'm not sure I understand why there needs to be a distinction, but we can discuss on #568 and update the wording in this docs page to match once we all agree. |
2 participants
A lot of small adjustments, and then a brand new page of docs.
docs/releases.rst