On Mon, Jul 17, 2017 at 10:11 AM, Matthias J. Sax
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" s
lopatierno<http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/>
From: Matthias J. Sax
Sent: Monday, July 17, 2017 5:11 PM
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-176: Remove deprecated new-consumer option i
Hi,
I agree that the option can be removed/deprecated.
However, I don't understand this:
> there will be no check that the new-consumer option is an invalid argument
> with the old consumer.
I thinks, for backward compatibility, this check should be there. The
only change should be, that if `-
Hi dev,
I'd like to discuss the possibility to remove the new-consumer option in the
ConsoleConsumer tool.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-176%3A+Remove+deprecated+new-consumer+option+in+ConsoleConsumer+tool
I have already opened a JIRA with related PR for marking it as
