RFC: Capability API#7700
Open
Xuanwo wants to merge 2 commits into
Open
Conversation
dosubot
Bot
added
size:L
erickguan
approved these changes
Jun 5, 2026
Comment on lines
+252
to
+253
| - Should `OperatorInfo::native_capability()` be deprecated immediately in all | ||
| bindings, or only in Rust first? |
Member
There was a problem hiding this comment.
I prefer announcing deprecation firstly and removing code in 1-2 release cycles.
Comment on lines
+254
to
+255
| - Should raw `AccessorInfo::service_capability()` be public within `opendal-core` | ||
| or restricted to crate-private APIs where possible? |
Member
There was a problem hiding this comment.
Private firstly. The idea of this usage is well considered. We could wait for user feedback.
Let's also document this.
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
2 participants
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?
N/A. This is an RFC PR; the tracking issue will be created after the RFC is accepted.
Rationale for this change
OpenDAL currently exposes both
native_capability()andfull_capability()to users, which makes feature availability checks harder to teach and easier to misuse.This RFC proposes
OperatorInfo::capability()as the single user-facing availability API while keeping service-declared capability as an internal boundary for services and layers.What changes are included in this PR?
This PR adds an RFC for renaming the capability API around effective operator capability and service-declared capability, without introducing a new
ServiceCapabilitytype.Are there any user-facing changes?
No code behavior changes are included in this PR. The RFC proposes future public API changes for Rust and bindings.
AI Usage Statement
AI assistance was used to draft this RFC.