#748 - Allow config consumer.max.poll.records #750
Conversation
This file contains 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
|
@confluentinc It looks like @MarkC0x just signed our Contributor License Agreement. 👍 Always at your service, clabot |
|
Hi @MarkC0x , Why this pull request is still open from last 3 years? Are we not planning to push this change? |
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.
Currently the consumer
max.poll.recordsconfiguration cannot be altered from the internally coded value of30. This PR allows the consumer value to be changed to the users choice by settingconsumer.max.poll.recordsin thekafka-rest.propertiesfile. If a different value is not set by the user, then the previous internally coded value of30will be used.