Skip to content
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

*: prepare for multi-key fetch #2

Merged
merged 1 commit into from
Jun 21, 2022
Merged

Conversation

GiedriusS
Copy link
Member

Upgrade internal interfaces for multi-key fetch:

  • Use multi-part HTTP request/response for retrieving data about
    multiple keys. Boundary is randomly generated by Go standard library so
    this seems like the best path;
  • Upgrade gRPC interface to have repeat string Keys instead of string Key. key has priority over keys but users should use keys either
    way.

Signed-off-by: Giedrius Statkevičius giedrius.statkevicius@vinted.com

@GiedriusS GiedriusS force-pushed the prepare_for_multi_key_fetch branch from 00c6fa7 to 7265abb Compare June 21, 2022 07:13
Upgrade internal interfaces for multi-key fetch:

- Use multi-part HTTP request/response for retrieving data about
multiple keys. Boundary is randomly generated by Go standard library so
this seems like the best path;
- Upgrade gRPC interface to have `repeat string Keys` instead of `string
Key`. `key` has priority over `keys` but users should use `keys` either
way.

Signed-off-by: Giedrius Statkevičius <giedrius.statkevicius@vinted.com>
Copy link

@marijus-ravickas marijus-ravickas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@GiedriusS GiedriusS merged commit 1b81014 into master Jun 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants