[
https://issues.apache.org/jira/browse/KAFKA-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Patierno resolved KAFKA-5588.
-----------------------------------
Resolution: Later
Before removing the --new-consumer option, the first step is to mark it as
deprecated in the next release. It will be removed in a new release cycle
(after deprecation).
> 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)
