feat: Updating producer to configure RoutingPolicy - adding partition_key as the default for Round Robin if set#366
Merged
BewareMyPower merged 13 commits intostreamnative:masterfrom Oct 24, 2025
Conversation
Contributor
Author
|
@BewareMyPower when you get a chance, please take another look. Updated with some additional tests and slightly changed the behavior to work with a stable vec of producers. |
Contributor
Author
|
Fixed the round robin unit test |
BewareMyPower
requested changes
Oct 21, 2025
BewareMyPower
approved these changes
Oct 23, 2025
Contributor
|
Please fix lint error |
BewareMyPower
approved these changes
Oct 24, 2025
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
2 participants
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.
Should address: #322
https://pulsar.apache.org/docs/next/client-libraries-producers/#choose-partitions-when-using-a-key
Copying the behavior in the Java Client, where the producer takes in a configuration for a RoutingPolicy (RoundRobin, Single or Custom) for publishing to a partitioned topic.
Non breaking behavior since if you don't specify a routing policy, it will automtically be Round Robin. Similarly to the Java Client, if you explicitly have a partition_key set in your message, it will deterministically hash the key and route to a partition that way