kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damian Guy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5327) Console Consumer should only poll for up to max messages
Date Thu, 01 Feb 2018 12:00:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Damian Guy updated KAFKA-5327:
------------------------------
    Fix Version/s:     (was: 1.1.0)
                   1.2.0

> 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: 1.2.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
(v7.6.3#76005)

Mime
View raw message