Replies: 3 comments 2 replies
-
@Xuanwo could you please provide the proper links to those traits? The github code search did not return anything and I want to make sure my potential contributions are well informed. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Shall we also retain |
Beta Was this translation helpful? Give feedback.
-
|
Tracked at #5739 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, everyone
I initially started building adapters like
kvandtyped_kvjust 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
kvandtyped_kvmore seriously, resulting in additional feature requests. For example, see #5701 and #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
KvReaderandKvWriter, 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
Accessdirectly and reuse the components we already have. This would allow the community to implement great features, such as reading ranges from SQLite, more easily.What do you think?
Beta Was this translation helpful? Give feedback.
All reactions