[fix][client] The partitionedProducer maxPendingMessages always is 0 #23593
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.
Motivation
After #13344, the default value of maxPendingMessages and maxPendingMessagesAcrossPartitions change to 0.
When creating a producer with the partitioned topic, setting one of the above configurations doesn't take effect; the actual value is always 0.
Because here have a minimum judgment.
pulsar/pulsar-client/src/main/java/org/apache/pulsar/client/impl/PartitionedProducerImpl.java
Lines 86 to 89 in 92448d5
Modifications
min
check when both values are not zero.Verifying this change
Documentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: