-
Notifications
You must be signed in to change notification settings - Fork 23
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
feat: get multi records by keys #410
Conversation
After talking with Alex, we agreed that using unary gRPC message would introduce less complexity and potentially less configuration / performance issues than opening many long lived streams (which by default are capped to 100 per server). |
Added some comments here and there. To me it looks like you only need |
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.
I have tested it against our internal server and internal tests. it looks good.
Code wise I don't see any particularity that could raise some issue.
/kind feat
What this PR does / Why we need it:
Performance optimization provided by a new endpoint to fetch records in batches by passing an array of keys.
Which issue(s) this PR fixes:
Closes #407
Special notes for your reviewer:
This new open saves interface leverage the GetMulti capabilities that was added to metaDB.