feat: url-pipeline core — parser, adapter ABC, registry, store hooks - #4192
Draft
jhamman wants to merge 1 commit into
Draft
feat: url-pipeline core — parser, adapter ABC, registry, store hooks#4192jhamman wants to merge 1 commit into
jhamman wants to merge 1 commit into
Conversation
d-v-b
reviewed
Jul 28, 2026
| """ | ||
| Abstract base class and data model for URL pipeline adapters. | ||
|
|
||
| A URL pipeline is a `|`-separated chain of sub-URLs, read outer-to-inner, |
Contributor
There was a problem hiding this comment.
probably need a link to jbms/url-pipeline so people can see the actual spec
jhamman
force-pushed
the
feature/url-pipeline-core
branch
2 times, most recently
from
July 28, 2026 14:52
10cb73b to
3aa63ac
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4192 +/- ##
==========================================
- Coverage 93.87% 93.40% -0.47%
==========================================
Files 91 93 +2
Lines 12594 12725 +131
==========================================
+ Hits 11822 11886 +64
- Misses 772 839 +67
🚀 New features to boost your workflow:
|
Implements URL pipeline support (https://github.com/jbms/url-pipeline): '|'-chained URLs resolve through pluggable adapters registered under the 'zarr.url_adapters' entry-point group (entry-point name = URL scheme). - zarr.abc.url_pipeline: PipelineSegment, AdapterResolution, PipelineContext, URLPipelineAdapter (single-classmethod contract) - zarr.storage._url_pipeline: parse_pipeline / resolve_pipeline; the root sub-URL delegates to make_store so existing file/memory/fsspec routing is unchanged - registry: register_url_adapter / get_url_adapter / list_url_adapter_schemes (name check only; no adapter imports) - make_store/make_store_path route strings containing '|' (or a registered root scheme) through the resolver; residual store paths combine with the user-supplied path - StorePath gains a zarr_format attribute (populated by format segments in a follow-up) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jhamman
force-pushed
the
feature/url-pipeline-core
branch
from
July 28, 2026 15:02
3aa63ac to
151be2d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR delivers the core infrastructure for plugable URL pipeline parsing.
Implements URL pipeline support (https://github.com/jbms/url-pipeline): '|'-chained URLs are resolves through pluggable adapters registered under the 'zarr.url_adapters' entry-point group (entry-point name = URL scheme).
zarr.abc.url_pipeline:PipelineSegment,AdapterResolution,PipelineContext,URLPipelineAdapter(single-classmethod contract)zarr.storage._url_pipeline:parse_pipeline/resolve_pipeline; the root sub-URL delegates to make_store so existing file/memory/fsspec routing is unchangedregistry:register_url_adapter/get_url_adapter/list_url_adapter_schemes(name check only; no adapter imports)make_store/make_store_pathroute strings containing '|' (or a registered root scheme) through the resolver; residual store paths combine with the user-supplied pathStorePathgains azarr_formatattribute (populated by format segments in a follow-up)For reviewers
This is PR 2 in a series towards #2943
Author attestation
TODO
docs/user-guide/*.mdchanges/