Tracking issues of RFC-3911: Deleter API
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 825
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 127
Description
- RFC: https://github.com/apache/incubator-opendal/pull/3911
## Tasks
- [x] https://github.com/apache/opendal/pull/5392
- Raw API: Add `oio::Delete`
- Raw API: Change `delete` to return `oio::Delete` in `Accessor`
- Raw API: Remove `batch` API
- Public API: Add `deleter` to `Operator`
- [x] Public API: Deprecate `remove`, `remove_via` APIs
- [x] Remove batch capability
- [ ] Add `recursive` support
- [x] https://github.com/apache/opendal/pull/6824
- [x] https://github.com/apache/opendal/pull/6827
- [x] azdls : https://github.com/apache/opendal/pull/7142
- [ ] webdav
- [ ] webhdfs
- [x] hdfs : https://github.com/apache/opendal/pull/7136
- [ ] hdfs_native
- [ ] dropbox
- [ ] Add `concurrent` support
## In the future
- [ ] Implement dtrace support for lister and deleter
- [ ] Implement oteltrace support for deleter
- [ ] implement batch delete for obs
- [ ] implement batch delete versioned object for oss
- [ ] Implement delete version check for deleter
Contributor guide
Research direction
Begin with RFC-3911 and the linked pull requests listed in the checklist to understand the Deleter API scope. Review the remaining recursive and concurrent support tasks, including webdav, webhdfs, hdfs_native, and dropbox; this issue is done when the applicable unchecked checklist items are completed or separately tracked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100