You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "Xuanwo (via GitHub)" <gi...@apache.org> on 2026/06/01 09:44:38 UTC
[I] Tracking Issue for RFC-7660: Move read range to reader [opendal]
Xuanwo opened a new issue, #7661:
URL: https://github.com/apache/opendal/issues/7661
Tracking issue for RFC #7660.
This tracks the raw read contract change proposed in the RFC:
- remove `BytesRange` from `OpRead`
- make `Access::read(path, OpRead)` return a reusable raw reader
- split the current range-scoped `oio::Read` into a range stream concept
- add raw reader methods for `stream(range)`, `read(range)`, and `fetch(ranges)`
- update layers to wrap the reusable raw reader instead of a single range stream
- update services to implement the new raw read contract
- preserve lazy `Operator::reader` behavior
- keep public `Reader` range planning policy in core, not in backend `Access`
Related problem issue: #7659.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Tracking Issue for RFC-7660: Move read range to reader [opendal]
Posted by "Xuanwo (via GitHub)" <gi...@apache.org>.
Xuanwo closed issue #7661: Tracking Issue for RFC-7660: Move read range to reader
URL: https://github.com/apache/opendal/issues/7661
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org