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

Fixed KeyShared routing when messages are sent in batches of 1 #7107

Merged
merged 1 commit into from
Jun 5, 2020

Conversation

merlimat
Copy link
Contributor

@merlimat merlimat commented May 29, 2020

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 6ca3a75

Motivation

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.

@merlimat merlimat added the type/bug The PR fixed a bug or issue reported a bug label May 29, 2020
@merlimat merlimat added this to the 2.6.0 milestone May 29, 2020
@merlimat merlimat self-assigned this May 29, 2020
@codelipenghui
Copy link
Contributor

/pulsarbot run-failure-checks

@codelipenghui codelipenghui merged commit 2d2c63e into apache:master Jun 5, 2020
@merlimat merlimat deleted the pr-ab9eafde7 branch June 5, 2020 15:20
cdbartholomew pushed a commit to kafkaesque-io/pulsar that referenced this pull request Jul 24, 2020
…e#7107)

Motivation
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.
huangdx0726 pushed a commit to huangdx0726/pulsar that referenced this pull request Aug 24, 2020
…e#7107)

Motivation
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants