-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Implemented response resolver (#1370, #1381) #1381
Conversation
Just realized there's probably a bug in I'll figure how to fix it soon-ish. ack @generall |
This was tedious to implement and annoying to test. @generall, can you make a final review, please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`clippy --tests` :/
- from public to private - from general logic to implementation detail
9881a70
to
b082d52
Compare
- Implement `Resolve` trait that "merges" multiple `retrieve`/`scroll_by`/`search` responses into a single response, to ensure it's consistent across multiple nodes in the cluster - Implement tests for the `Resolve` trait implementation - Add a few additional derives required for the `Resolve` trait implementation Co-authored-by: Andrey Vasnetsov <andrey@vasnetsov.com>
Implemented logic that "merge" multiple
Vec<Record>
/Vec<ScoredPoint>
responses into a single response.The merged response only retains items that are present either in majority (more than half) or all of the original responses.
TODO:
execute_read_operation