kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vahid Hashemian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5588) ConsumerConsole : uselss --new-consumer option
Date Thu, 13 Jul 2017 17:25:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086040#comment-16086040
] 

Vahid Hashemian commented on KAFKA-5588:
----------------------------------------

If I'm not mistaken this requires a KIP due to potential impact to existing users.

> ConsumerConsole : uselss --new-consumer option
> ----------------------------------------------
>
>                 Key: KAFKA-5588
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5588
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Paolo Patierno
>            Assignee: Paolo Patierno
>            Priority: Minor
>
> Hi,
> it seems to me that the --new-consumer option on the ConsoleConsumer is useless.
> The useOldConsumer var is related to specify --zookeeper on the command line but then
the ----bootstrap-server option (or the --new-consumer) can't be used.
> If you use --bootstrap-server option then the new consumer is used automatically so no
need for --new-consumer.
> It turns out the using the old or new consumer is just related on using --zookeeper or
--bootstrap-server option (which can't be used together, so I can't use new consumer connecting
to zookeeper).
> It's also clear when you use --zookeeper for the old consumer and the output from help
says :
> "Consider using the new consumer by passing [bootstrap-server] instead of [zookeeper]"
> I'm going to remove the --new-consumer option from the tool.
> Thanks,
> Paolo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message