Xuanwo opened a new issue, #5739: URL: https://github.com/apache/opendal/issues/5739
As discussed in https://github.com/apache/opendal/discussions/5703: > I initially started building adapters like `kv` and `typed_kv` just for fun, exploring the potential of OpenDAL. These adapters were designed to be simple and primarily optimized for implementing services in an easy way. > > However, over time, some users have begun using services built on `kv` and `typed_kv` more seriously, resulting in additional feature requests. For example, see https://github.com/apache/opendal/discussions/5701 and https://github.com/apache/opendal/issues/5623. > > Those factors combined made me wonder whether it's a good idea for us to keep both of those adapters. It seems we can simply retain `KvReader` and `KvWriter`, allowing services to use them directly instead of having to implement them each time. This also unlocks the potential for services to introduce more features without adding another layer of unnecessary abstraction. > > Maybe we could migrate services to implement `Access` directly and reuse the components we already have. This would allow the community to implement great features, such as reading ranges from SQLite, more easily. Let's start migrating adapter based services. This migration should not break any existsing services. ## Tasks - [ ] atomicserver - [ ] cacache - [ ] cloudflare_kv - [ ] d1 - [ ] dashmap - [ ] etcd - [ ] foundationdb - [ ] memcached - [ ] memory - [ ] mini_moka - [ ] moka - [ ] mongodb - [ ] nebula_graph - [ ] persy - [ ] redb - [ ] redis - [ ] rocksdb - [ ] sled - [ ] sqlite - [ ] surrealdb -- 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]
