Support Kafka's ProducerConfig.REQUEST_TIMEOUT_MS_CONFIG. #3797
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.
Motivatio
Support Kafka's ProducerConfig.REQUEST_TIMEOUT_MS_CONFIG #1090
Previously
ProducerBuilder.sendTimeout
was set by parsing Kafka'sProducerConfig.MAX_BLOCK_MS_CONFIG
.According to Kafka's document it's for
But
ProducerBuilder.sendTimeout
is forAnd Kafka's
ProducerConfig.REQUEST_TIMEOUT_MS_CONFIG
, according to the document is for:Which I think would be better fit purpose of Pulsar's
ProducerBuilder.sendTimeout
.