cmccabe commented on PR #13111: URL: https://github.com/apache/kafka/pull/13111#issuecomment-1384914114
I hate to say this, but I think this should probably be WONTFIX. The rule for admin tools that used the `--zookeeper` flag was always that you needed to match the admin tool version and the software version. Even using the admin tool for version 2.8 on version 2.7 would have been considered a major operator error. The scenario here we're discussing is using the 2.8 tool on a 3.x version. So a different major version (not even minor), and version that was released several years later. That's way outside of what we ever supported with the `--zookeeper` flag. Let me give an example of the general kind of problem you could have here. If you created a prefix ACL using an admin tool that had the --zookeeper flag, but your kafka version didn't support prefix ACLs, what would happen? I'm not completely sure, but nothing good. This is the same kind of thing -- old software overwriting whatever the new software has put in the znode. So it's not just topic IDs, but in general anything new that we add, that will get overwritten. We can't really support this -- we never promised to keep that znode the same forever. Stuff like this is why the --zookeeper flags were removed. We do support cross-version compatibility when using the --bootstrap-server option. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
