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-5588) Remove deprecated new-consumer option for tools
Date Tue, 26 Sep 2017 07:30:00 GMT

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

Paolo Patierno updated KAFKA-5588:
----------------------------------
    Description: 
Hi,
with the current version of the ConsoleConsumer, ConsumerPerformance and ConsumerGroupCommand
command line tools, it's not needed to specify the --new-consumer option anymore in order
to use the new consumer. The choice for using the old or the new one is made just specifying
the --zookeeper for the former and --bootstrap-server for the latter.

The issues [KAFKA-5599|https://issues.apache.org/jira/browse/KAFKA-5599] and [KAFKA-5619|https://issues.apache.org/jira/browse/KAFKA-5619]
fixed and included in the 1.0.0 release deprecated the usage of the --new-consumer flag.

More details in the related [KIP-176|https://cwiki.apache.org/confluence/display/KAFKA/KIP-176%3A+Remove+deprecated+new-consumer+option+for+tools].

Thanks,
Paolo.


  was:
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.



> Remove deprecated new-consumer option for tools
> -----------------------------------------------
>
>                 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,
> with the current version of the ConsoleConsumer, ConsumerPerformance and ConsumerGroupCommand
command line tools, it's not needed to specify the --new-consumer option anymore in order
to use the new consumer. The choice for using the old or the new one is made just specifying
the --zookeeper for the former and --bootstrap-server for the latter.
> The issues [KAFKA-5599|https://issues.apache.org/jira/browse/KAFKA-5599] and [KAFKA-5619|https://issues.apache.org/jira/browse/KAFKA-5619]
fixed and included in the 1.0.0 release deprecated the usage of the --new-consumer flag.
> More details in the related [KIP-176|https://cwiki.apache.org/confluence/display/KAFKA/KIP-176%3A+Remove+deprecated+new-consumer+option+for+tools].
> Thanks,
> Paolo.



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

Mime
View raw message