[
https://issues.apache.org/jira/browse/KAFKA-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson reopened KAFKA-5327:
------------------------------------
I have reverted this change in KAFKA-5414 since it breaks existing usage. It
seems like a simpler option is just to ensure that max.poll.records is not set
higher than max messages.
> Console Consumer should only poll for up to max messages
> --------------------------------------------------------
>
> Key: KAFKA-5327
> URL: https://issues.apache.org/jira/browse/KAFKA-5327
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Reporter: Dustin Cote
> Assignee: huxihx
> Priority: Minor
> Fix For: 0.11.0.0
>
>
> The ConsoleConsumer has a --max-messages flag that can be used to limit the
> number of messages consumed. However, the number of records actually consumed
> is governed by max.poll.records. This means you see one message on the
> console, but your offset has moved forward a default of 500, which is kind of
> counterintuitive. It would be good to only commit offsets for messages we
> have printed to the console.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
