Hi Andrew, Thanks for the KIP. The mixed dash and dot syntax in --producer.config and --consumer.config has always vexed me. I just have one thought:
To be honest, like Kirk, I don't love --command-config. While it is the most common flag name for specifying client properties, it seems both inaccurate ("command" to me implies the actual CLI tool invocation, but you can't us it to configure, e.g., the name of the topic being written to/read from with the console producer/consumer) and vague (I would never anticipate this name on my own when running any of the CLI tools for the first time). How would you feel about --client-config? Cheers, Chris On Wed, Jul 9, 2025 at 9:07 PM Kirk True <k...@kirktrue.pro> wrote: > Hi Andrew, > > Thanks for the KIP. Yes, the inconsistency drives me crazy :) > > Just one initial question: > > KT01: During the migration period where both command line arguments are > supported (e.g. --producer-props and --producer-property), which takes > precedence? > > I'm not ecstatic about the existing naming of "--command-config" because > it's ambiguous, but that's a battle for another day... > > Thanks, > Kirk > > On Wed, Jul 9, 2025, at 6:53 AM, Andrew Schofield wrote: > > Hi, > > I'd like to start discussion of KIP-1147. This KIP aligns the names of > the command-line > > arguments across all of the Apache Kafka command-line tools. > > > > KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1147%3A+Improve+consistency+of+command-line+arguments > > > > Thanks, > > Andrew >