Tracking issues for migrating Java bindings to RFC-6213 Options API
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 825
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 127
Description
Following RFC-6213 (#6213), OpenDAL has introduced a new options-based API pattern to replace the builder pattern for operations (e.g. `write_with().append(true)`). The new approach simplifies cross language binding parity for capabilities and supported options across all language bindings!
The following Options need to be added or migrated to use this new API in the Java bindings:
- [x] WriteOptions: #6219
- [ ] ReadOptions (needs migration and partially added)
- [x] StatOptions: #6255
- [ ] DeleteOptions (not implemented)
- [x] ListOptions #6246
Contributor guide
Research direction
Start by reading RFC-6213 and the completed tracking items #6219, #6255, and #6246 to understand the Options API pattern. Review the partially added ReadOptions work, then determine the remaining ReadOptions migration and the unimplemented DeleteOptions scope. Done means both unchecked items are completed in the Java bindings; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100