This repository was archived by the owner on Oct 5, 2025. It is now read-only.
Add Service Provider Interface for extensible RangeReader discovery#74
Merged
Add Service Provider Interface for extensible RangeReader discovery#74
Conversation
groldan
added
documentation
📖 Documentation Preview Ready!The documentation has been built for this PR and is ready for review. 🔗 Preview Options:
📊 Build Information:
🧪 What's Included:
💡 Tip: To test locally, run |
📚 Documentation Validation ResultsThe documentation has been built and validated successfully! ✅ Validation Checks Passed:
📋 Summary:
You can preview the built documentation by downloading the |
📈 Documentation Impact Analysis📊 Documentation Changes Summary
📄 New Pages:🗑️ Removed Pages:✏️ Modified Pages:
Analysis generated on Sun Sep 7 02:40:19 UTC 2025 This analysis compares the built documentation between the base branch and this PR. |
groldan
force-pushed
the
factory_spi
branch
2 times, most recently
from
3a36de9 to
e5e18c0
Compare
Introduce RangeReaderProvider SPI to enable automatic discovery and selection of RangeReader implementations based on URI schemes and endpoint patterns. The SPI includes disambiguation for overlapping protocols (HTTP/HTTPS) using HTTP response header analysis. The RangeReaderFactory now serves as the unified entry point, automatically selecting the most appropriate provider for any given URI. This enables seamless extension with new storage backends without requiring modifications to the core library. The implementation supports automatic provider discovery via ServiceLoader, URI scheme-based filtering with hostname pattern matching, HTTP header inspection for cloud provider disambiguation, and priority-based selection for ambiguous cases. All existing RangeReader implementations have their dedicated provider classes. Additionally includes fixes for S3 region detection from virtual hosted-style URLs and enhanced GCS URI parsing to support both public URLs and REST API endpoints used by emulators.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Introduce RangeReaderProvider SPI to enable automatic discovery and selection of RangeReader implementations based on URI schemes and endpoint patterns. The SPI includes disambiguation for overlapping protocols (HTTP/HTTPS) using HTTP response header analysis.
The RangeReaderFactory now serves as the unified entry point, automatically selecting the most appropriate provider for any given URI. This enables seamless extension with new storage backends without requiring modifications to the core library.
The implementation supports automatic provider discovery via ServiceLoader, URI scheme-based filtering with hostname pattern matching, HTTP header inspection for cloud provider disambiguation, and priority-based selection for ambiguous cases. All existing RangeReader implementations have their dedicated provider classes.
Additionally includes fixes for S3 region detection from virtual hosted-style URLs and enhanced GCS URI parsing to support both public URLs and REST API endpoints used by emulators.