-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HADOOP-19105. Improve resilience in vector reads. #7105
Draft
steveloughran
wants to merge
4
commits into
apache:trunk
Choose a base branch
from
steveloughran:s3/HADOOP-19105-vectorio-recovery
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
HADOOP-19105. Improve resilience in vector reads. #7105
steveloughran
wants to merge
4
commits into
apache:trunk
from
steveloughran:s3/HADOOP-19105-vectorio-recovery
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
Add a new releaser method, which then is invoked to release buffers on failure. It is a bit contrived how we try not break external implementations when adding a new default implementation to PositionedReadable: the releaser will be lost unless they do so. Change-Id: Ie2f95a89cfa79d3fdf33c1cc58f63e4ca00c6207
💔 -1 overall
This message was automatically generated. |
Trying to implement resilience in the s3a input stream; buffers of incomplete reads are now released on failures. Change-Id: I4b23c6a2ff417687fd19c1e8e9feef6cf733c031
Trying to implement resilience in the s3a input stream; buffers of incomplete reads are now released on failures. Change-Id: I851779383f8d120fe42bc97c5e6ae533c5fe2e23
💔 -1 overall
This message was automatically generated. |
Now: how do I pull this out so it can be used with the prefetch stream? Change-Id: I98e350ab3b28d9adc7b458dee4ceee56a0562f17
💔 -1 overall
This message was automatically generated. |
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.
Add a new releaser method, which then is invoked to release buffers on failure.
It is a bit contrived how we try not break external implementations when adding a new default implementation to PositionedReadable: the releaser will be lost unless they do so.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?