[
https://issues.apache.org/jira/browse/KAFKA-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942699#comment-14942699
]
ASF GitHub Bot commented on KAFKA-2603:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/274
KAFKA-2603: Add timeout arg to ConsoleConsumer
Added --timeout-ms argument to ConsoleConsumer that works with both old and
new consumer. Also modified ducktape ConsoleConsumer service to use this arg
instead of consumer.timeout.ms config that works only with the old consumer.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-2603
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/274.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #274
----
commit f76a27d6c7580bd38f1fe6792f8f4754485b3787
Author: Rajini Sivaram <rajinisiva...@googlemail.com>
Date: 2015-10-04T16:08:25Z
KAFKA-2603: Add timeout arg to ConsoleConsumer that works with old and new
consumer, use arg in ducktape service
----
> Add timeout to ConsoleConsumer running with new consumer
> --------------------------------------------------------
>
> Key: KAFKA-2603
> URL: https://issues.apache.org/jira/browse/KAFKA-2603
> Project: Kafka
> Issue Type: Test
> Affects Versions: 0.9.0.0
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Fix For: 0.9.0.0
>
>
> ConsoleConsumer exits when no messages are received for a timeout period when
> run with the old consumer since the old consumer had a timeout parameter.
> This behaviour is not available with the new consumer and hence ducktape
> tests which rely on the timeout cannot be run with the new consumer.
> [~granders] has suggested a solution in KAFKA-2581.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
