docs: Unify capabilities list for kv services #2257
Merged
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.
In the very first, I want to migrate
sled
/rocksdb
services totyped_kv
. But I foundtyped_kv
has its own data schema (metadata
+value
), it seems would break loading and writing of existed data? Discussion is required here.Then I found the type
crate::Capability
doesn't havescan
flag, is this intentional result or deliberate design?Then for this PR,
scan
flag to generalCapability
Notes:
cargo test
passed locally.scan
flag for those services capable withscan
haven't set totrue
yet.Further discussions:
typed_kv
migration forsled
/rocksdb
/memorycache
/redis
BlockCapability
; 2.ObjectCapability
, 3.KvCapability
This's my first PR for OpenDAL 😀 Please check more in details.
Thanks for your efforts!
Sincerely,
Lanqing