lqhuang opened a new pull request, #2257: URL: https://github.com/apache/incubator-opendal/pull/2257
In the very first, I want to migrate `sled`/`rocksdb` services to `typed_kv`. But I found `typed_kv` has its own data schema (`metadata` + `value`), it seems would broken existed data? Discussion is required here. Then I found the type [`crate::Capability`](https://github.com/apache/incubator-opendal/blob/5d890603a48b1f51c85012fcd22388643d860104/core/src/types/capability.rs#LL48C1-L48C24) doesn't have `scan` flag, is this intentional result or deliberate design? Then for this PR, 1. Add a `scan` flag to general `Capability` 2. Simply reformat capabilities docs of all KV services to the same. Notes: 1. `cargo test` passed locally. 2. `scan` flag for those services capable with `scan` haven't set to `true` yet. Further discussions: 1. Should we have similar `typed_kv` migration for `sled`/`rocksdb`/`memorycache`/`redis` 2. Should we split services into different categories (and project layout): 1. Block Storage 2. Object Storage 3. KV Storage, more over also have different capabilities: 1. `BlockCapability`; 2. `ObjectCapability`, 3. `KvCapability` This's my first PR for OpenDAL 😀 Please check more in details. Thanks for your efforts! Sincerely, Lanqing -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
