Hi Christo, Thanks for the comment!
The version-mapping and feature-dependencies commands were added In KIP- 1022<https://cwiki.apache.org/confluence/display/KAFKA/KIP-1022%3A+Formatting+and+Updating+Features>. Based on the discussion<https://lists.apache.org/thread/l1qszyjrnppz27ggcqr91q8b1b8tdstl>, they should work offline in both tools. In my point of view, users may be confused by the inconsistency and doubt the two tools provide different information. Yes. I believe that the flag is required in some testing senario. Before KAFKA-19544, the version-mapping command doesn’t include unstable feature versions. Now, the tool includes them without asking users. Adding a flag whose default is false can prevent normal users from accidently using an unstable feature versions while allowing advanced user to query on those versions. Best, Chang-Yu Huang From: Christo Lolov <[email protected]> Date: Monday, October 27, 2025 at 10:43 AM To: [email protected] <[email protected]> Subject: Re: [DISCUSS] KIP-1234: Move and Add Arguments to version-mapping Commands Heya, Thanks for the KIP! I am not convinced that making --bootstrap-server/--bootstrap-controller optional in kafka-features is needed. I understand that there is a difference with how kafka-storage works, but the two CLIs are meant to be used in different situations - kafka-storage is meant to be used during a setup leading to a working cluster while kafka-features allows dynamic interactions with an already working cluster. I further understand that you might want to use this tool in an automation, but I don't quite understand to what purpose - this isn't dynamic information i.e. it will only change during a new release and you can just point to that release's kafka-storage tool to get the same information, no? I am more intrigued by the second part of the KIP. As far as I am understanding it, you would like to see what features are unstable, or at least which version numbers of a feature are unstable so that you don't enable them accidentally? Best, Christo
