kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Patierno (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5599) ConsoleConsumer : --new-consumer option as deprecated
Date Fri, 28 Jul 2017 08:05:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Paolo Patierno updated KAFKA-5599:
    Fix Version/s: 1.0.0

> 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
>             Fix For: 1.0.0
> 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

View raw message