[
https://issues.apache.org/jira/browse/KAFKA-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011261#comment-14011261
]
Jun Rao commented on KAFKA-924:
-------------------------------
Thanks for the patch. This seems to have broken our system tests though. Our
system tests rely on console consumer to verify the output, which now fails
with the following.
bin/kafka-run-class.sh kafka.consumer.ConsoleConsumer --zookeeper
localhost:2181 --topic test --consumer-timeout-ms 10000 --csv-reporter-enabled
--from-beginning
'consumer-timeout-ms' is not a recognized option
Perhaps the easiest fix is to resurrect the --consumer-timeout-ms for backward
compatibility.
> Specify console consumer properties via a single --property command line
> parameter
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-924
> URL: https://issues.apache.org/jira/browse/KAFKA-924
> Project: Kafka
> Issue Type: Bug
> Reporter: Swapnil Ghike
> Assignee: Sriharsha Chintalapani
> Labels: newbie
> Fix For: 0.8.2
>
> Attachments: KAFKA-924.patch, KAFKA-924_2014-05-23_14:47:30.patch,
> KAFKA-924_2014-05-27_14:51:31.patch
>
>
> Quoting Neha from KAFKA-917:
> I think the right way to add access to all consumer properties is to specify
> it through a single --property command line parameter that takes in
> "key1=value1,key2=value2,..." list. That will make sure we don't have to keep
> changing console consumer as well add/remove config options on the consumer.
> Some configs make sense to be top level for console consumer though. Things
> like topic, from-beginning, groupid etc. Rest can be specified through the
> "property" parameter.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
