-
Notifications
You must be signed in to change notification settings - Fork 664
#748 - Allow config consumer.max.poll.records #750
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ghost
commented
Sep 18, 2020
@confluentinc It looks like @MarkC0x just signed our Contributor License Agreement. 👍
Always at your service,
clabot
kasarlaharish1
commented
Oct 21, 2023
Hi @MarkC0x ,
Why this pull request is still open from last 3 years? Are we not planning to push this change?
CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
Mark Cox seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.
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.