RFC-7660: Move Read Range To Reader#7660
Open
Xuanwo wants to merge 3 commits into
Open
Conversation
dosubot
Bot
added
size:L
Xuanwo
changed the title
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
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.
Which issue does this PR close?
Refs #7659.
Rationale for this change
OpenDAL's raw
Access::readcurrently owns the byte range, which makes every planned range create a new range stream. This creates repeated open and close overhead for handle based services.What changes are included in this PR?
This adds an RFC that proposes moving byte ranges from
Access::readinto methods on the returned raw reader, includingstream,read, andfetch.Are there any user-facing changes?
No. This is an RFC only.
AI Usage Statement
AI-assisted drafting was used for the RFC text.