I found that the deprecation was added speaking about the KIP-109<https://cwiki.apache.org/confluence/display/KAFKA/KIP-109%3A+Old+Consumer+Deprecation> which discuss the old consumer deprecation.
So the TopicFilter is used in deprecated classes like OldConsumer, ConsumerConnector and so on but even in the MirrorMaker which isn't deprecated but still in Scala so it could be part of the process to move all tools from Scala to Java. At same time the new consumer just accept a Pattern in the subscribe and doesn't use the TopicFilter. Even with TopicCommand, the --topic can be a pattern. My understanding is that we can get rid of TopicFilter, Whitelisy and Blacklist even from the TopicCommand. 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: Paolo Patierno <ppatie...@live.com> Sent: Tuesday, July 18, 2017 3:53 PM To: dev@kafka.apache.org Subject: Reason why TopicFilter and related classes are deprecated Hi devs, why the TopicFilter and related Whitelist and Blacklist classes are marked as deprecated ? They are used for filtering on topic with a regex in the ConsoleConsumer, MirrorMaker, TopicCommand ... Do you have a plan for them to be replaced or not, so marking them as deprecated ? Working on rewriting the TopicCommand tool using the Admin Client API this question came up to my mind. 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/>
