Hi all, I have updated the KIP-176 <https://cwiki.apache.org/confluence/display/KAFKA/KIP-176%3A+Remove+deprecated+new-consumer+option+for+tools> in order to consider to remove the --new-consumer option not only for ConsoleConsumer but even for other tools which use it : ConsumerPerformance and ConsumerGroupCommand.
I'm also working on a PR for a new-consumer option deprecation as first step for ConsumerPerformance and ConsumerGroupCommand (as already done, pushing a PR<https://github.com/apache/kafka/pull/3537>, for ConsoleConsumer). Thanks, Paolo Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : DevExperience<http://paolopatierno.wordpress.com/> ________________________________ From: isma...@gmail.com <isma...@gmail.com> on behalf of Ismael Juma <ism...@juma.me.uk> Sent: Tuesday, July 18, 2017 1:09 PM To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-176: Remove deprecated new-consumer option in ConsoleConsumer tool On Mon, Jul 17, 2017 at 10:11 AM, Matthias J. Sax <matth...@confluent.io> wrote: > I thinks, for backward compatibility, this check should be there. The > only change should be, that if `--bootstrap-servers` is used, one can > omit `--new-consumer` (and if used, as warning is printed). > You can omit "--new-consumer" since 0.10.2. Paolo's PR will add the warning so that we can eventually remove the switch altogether. To be honest, we could just remove it at the same time as we remove the old consumer. Ismael
