Hi committers, in my understanding there is the common idea to move all tools from Scala to Java and then using the new Admin Client API instead of using the Zookeeper connection.
Regarding this subject I started to work on refactoring the TopicCommand tool but with two steps at same time : * re-writing it in Java * removing --zookeeper option (so no Zookeeper connection) and adding --broker-list option (so using the Admin Client API) Of course, such option substitution is a breaking change for the tool (and the users who are using it). In such a scenario, the two steps path should be needed : first deprecation, then removal (for the --zookeeper option) It seems that in the "deprecation" phase we have two possible solutions : 1. Adding Admin Client API to the Scala tools and so the --broker-list option and a warning on --zookeeper for deprecation 2. Rewriting the tool in Java using the Admin Client API (so --broker-list) but at same time providing --zookeeper as well (so Zookeeper connection) With the solution 2) we have the advantage to have the tool already in Java when the --zookeeper option will be removed in a next step. In any case we have to write the part related to use the Admin Client API so it make more sense to me option 2) porting the Zookeeper needed code from Scala to Java (then removing it in the next phase). Is my understanding right on how we have to handle deprecation and removal for something that is a breaking change ? Or this case is something "special" and we can live with a new Java based tool without zookeeper but with Admin Client API at same time ? Of course having both Admin Client API and Zookeeper utils working at the same time in the tools means more complexity in the code but it's something that could be factorized. 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/>
