feat(routing): add internal request/response policy enums #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ofekshenawa
merged commit 9e4369a
into
load-balance-search-commands-to-shards
3 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce
internal/routing/policy.go:RequestPolicyenum covering: default, all_nodes, all_shards,multi_shard and special – exactly matching the new Redis
request_policytip.ResponsePolicyenum with aggregation / success-criteria values.CommandPolicystruct that bundles both enums for fast lookup.String()andParse*()helpers for round-tripping between rawCOMMAND tips and the enums.