Skip to content
Discussion options

You must be logged in to vote

Thanks for the use case.
To clarify the current state: d-engine doesn't support prefix/range scan for batch reads yet.
We do have #300 (Prefix Watch) in planning, which addresses prefix matching on the watch/event side, so it will partially help — for example, monitoring key changes under a namespace. However, it won't cover your batch read use case (one-shot scan of all keys matching a prefix).
That's a separate capability closer to a range scan. It's already on our roadmap for v0.3.x as part of making d-engine a lightweight KV store. You can track the overall direction here: #281

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by l-7-l
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants