[ https://issues.apache.org/jira/browse/KAFKA-7795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Arthur updated KAFKA-7795: -------------------------------- Description: It would be nice to perform some basic validation of the broker config so that things aren't unexpectedly overwritten. For example, {code:java} unclean.leader.election.enable=false // many other lines of config unclean.leader.election.enable=true {code} By detecting duplicate keys in the config file, we can inform users that there is a config problem. Note that this will not prevent the broker from starting, but rather it will produce some log warnings. was: It would be nice to perform some basic validation of the broker config so that things aren't unexpectedly overwritten. For example, {code:java} unclean.leader.election.enable=false // many other lines of config unclean.leader.election.enable=true {code} By detecting duplicate keys in the config file, we can avoid such situations. > Produce a warning when duplicate config keys are detected > --------------------------------------------------------- > > Key: KAFKA-7795 > URL: https://issues.apache.org/jira/browse/KAFKA-7795 > Project: Kafka > Issue Type: Improvement > Components: config > Reporter: David Arthur > Priority: Minor > > It would be nice to perform some basic validation of the broker config > so that things aren't unexpectedly overwritten. > For example, > {code:java} > unclean.leader.election.enable=false > // many other lines of config > unclean.leader.election.enable=true > {code} > By detecting duplicate keys in the config file, we can inform users that > there is a config problem. > Note that this will not prevent the broker from starting, but rather it will > produce some log warnings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)