-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multi spans and on Document Fetcher. #60
Comments
hey @AndrewSisley peeked at some of the commits youre working on for this issue in the As far as I can tell, you are re-binding the dependancy the internals of the DB has on badger itself. Much of the goal of relying on the Specifically, updating the core/client interfaces Line 40 in a463b6b
I think the multispan stuff should be applied to either
|
Ah don't worry about that - that is an interface I defined in the v3 package, that is not specific to badger db - it just lives there in the extreme-short-term because thats where I happened to write it down first :) none of the defra stuff in that branch should currently be (directly) dependent on any badger stuff. If I'm understanding what you mean correctly at least :) Will have a re-read once I'm properly working again (just saw this in my inbox) |
Marking as blocked until the benchmarks are ready - code is not properly cleaned up yet (re readability/location/etc), but the main happy path should be fairly static now computationally and we should find out whether it is worth it performance wise before continuing |
Currently, we only support single spans on our document fetcher, moreover, it only supports prefix scans and ignores the "end" range stop point.
To make the fetcher more efficient we need to support mutlispans and proper range scans.
The blocking issue is go-datastore#116. Needs proper architecture/implementation on the interface package, and a series of datastore implementations. That issue will give context.
The text was updated successfully, but these errors were encountered: