Fixed KeyShared routing when messages are sent in batches of 1 #7107
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.
Note: this is based on top of #6791, #7104, #7105 and #7106. Once these are merged, I'll rebase here. For the sake of this review, check commit 6ca3a75Motivation
When messages are published in batches of 1 message (eg: from Go native client lib), the KeyShared dispatcher is failing to extract the key from the first message in batch, instead everything is routed using
NONE_KEY
, landing on 1 single consumer.