Tracking issues of RFC-5485: Conditional Reader
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 825
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 127
Description
- RFC: https://github.com/apache/opendal/pull/5485
## Tasks
- [x] https://github.com/apache/opendal/pull/5492
- [x] add `if_match` and `if_none_match` for `FutureReader`
- [x] https://github.com/apache/opendal/pull/5500
- [x] implement `if_modified_since` and `if_unmodified_since` for `FutureReader` and `FutureRead`
- [x] implement tests for reader with `if_modified_since` and `if_unmodified_since`
- [x] implement `if_modified_since` and `if_unmodified_since` for `S3`
- [ ] implement read with `if_modified_since` and `if_unmodified_since` for services
- [x] azblob, oss: https://github.com/apache/opendal/pull/5531
- [ ] cos
- [ ] swift
- [ ] http
- [ ] ...
- [ ] implement read with `if_match` and `if_none_match` for services
- [ ] swift
- [ ] webdav
- [ ] lakefs
- [ ] ...
Contributor guide
Research direction
Start with RFC-5485 and the completed PRs 5492, 5500, and 5531 to understand the conditional reader behavior. Choose one unchecked service, such as COS, Swift, HTTP, WebDAV, or LakeFS, and trace its read implementation. Done means the selected service supports the listed conditional-read options and its entry is completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100