[
https://issues.apache.org/jira/browse/KAFKA-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089684#comment-16089684
]
Ismael Juma commented on KAFKA-5599:
------------------------------------
For background, there was a time when "--new-consumer" was required to use the
new consumer. We changed that in a recent release because we wanted the new
consumer to become the default. The idea was to deprecated and eventually
remove "--new-consumer" in subsequent releases.
> ConsoleConsumer : --new-consumer option as deprecated
> -----------------------------------------------------
>
> Key: KAFKA-5599
> URL: https://issues.apache.org/jira/browse/KAFKA-5599
> Project: Kafka
> Issue Type: Bug
> Components: tools
> Reporter: Paolo Patierno
> Assignee: Paolo Patierno
>
> 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]"
> Before removing the --new-consumer option, this JIRA is for marking it as
> deprecated in the next release (then moving for a new release on removing
> such option).
> Thanks,
> Paolo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
