[java-client] Add support for key hash range reading.#5928
Merged
codelipenghui merged 3 commits intoapache:masterfrom Jan 9, 2020
Merged
[java-client] Add support for key hash range reading.#5928codelipenghui merged 3 commits intoapache:masterfrom
codelipenghui merged 3 commits intoapache:masterfrom
Conversation
12 tasks
Contributor
Author
|
run java8 tests |
Contributor
Author
|
run cpp tests |
Contributor
Author
|
rerun java8 tests |
1 similar comment
Contributor
Author
|
rerun java8 tests |
Contributor
Author
|
run java8 tests |
Contributor
Author
|
run java8 tests |
2 similar comments
Contributor
Author
|
run java8 tests |
Contributor
Author
|
run java8 tests |
Contributor
Author
|
rerun java8 tests |
2 similar comments
Contributor
Author
|
rerun java8 tests |
Contributor
Author
|
rerun java8 tests |
15 tasks
sijie
approved these changes
Jan 6, 2020
6c2851c to
5608be9
Compare
Contributor
Author
|
retest this please |
1 similar comment
Contributor
Author
|
retest this please |
5608be9 to
8d297ed
Compare
Member
|
run java8 tests |
Contributor
Author
|
run integration tests |
huangdx0726
pushed a commit
to huangdx0726/pulsar
that referenced
this pull request
Aug 24, 2020
### Motivation
Add support for sticky key hash range reader. Broker will only dispatch messages which hash of the message key contains by the specified key hash range.
Multiple key hash ranges can be specified on a reader by following example:
```java
pulsarClient.newReader()
.topic(topic)
.startMessageId(MessageId.earliest)
.keyHashRange(Range.of(0, 10000), Range.of(20001, 30000))
.create();
```
Member
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
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.

Master Issue: #4077
Motivation
Add support for sticky key hash range reader. Broker will only dispatch messages which hash of the message key contains by the specified key hash range.
Multiple key hash ranges can be specified on a reader by following example:
Verifying this change
New unit tests was added for cover this change
Does this pull request potentially affect one of the following parts:
If
yeswas chosen, please highlight the changesDocumentation