Range-based reading of HTTP resources #2067
Merged
Conversation
This file contains 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
moradology
force-pushed
the
feature/http-range-reader
branch
from
e52bd7d
to
71533f8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds support for Reading TIFF data stored at HTTP locations which expose the ability to specify byte-based range reading.
The library included (
scalaj-http) is a very thin wrapper around Java'sHttpUrlConnection. It provides some useful features (it is syntactically far superior to the java it wraps), cleans up after itself, brings in no further dependencies, and is licensed under Apache 2.0.Testing required adding another container. Testing should now kick off a container which serves contents from
spark/src/test/resourcesand accepts range-based reads.