[
https://issues.apache.org/jira/browse/KAFKA-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042234#comment-17042234
]
Jason Gustafson commented on KAFKA-9593:
----------------------------------------
The message could be improved here, but I think the main problem is that the
config tool is not using the incremental config API. I filed a JIRA for this:
https://issues.apache.org/jira/browse/KAFKA-9595. For the problem of an
incorrect config, I am not sure the broker can do stricter validation because
some plugins may rely on configurations that are not known to it. However, when
this happens, you can delete the invalid configuration using `--delete-config`.
> Kafka config allows updating a nonexistent config and makes it mandatory to
> specify the config for further config updates
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-9593
> URL: https://issues.apache.org/jira/browse/KAFKA-9593
> Project: Kafka
> Issue Type: Bug
> Reporter: Aishwarya Gune
> Priority: Major
>
> When using kafka-config script to update config, attempt to update a
> non-existing config goes through. For example -
> {noformat}
> ./bin/kafka-configs.sh --bootstrap-server localhost:9092 --alter
> --add-config 'log.cleaner.threads.config=50' --entity-default --entity-type
> brokers
> {noformat}
> The correct config name is - `log.cleaner.threads`.
> Following the above command, if the correct config is to be updated it hits
> the following issue -
> {noformat}
> All sensitive broker config entries must be specified for --alter, missing
> entries: Set(log.cleaner.threads.config)
> {noformat}
> One way to update this config now is to specify the incorrect config too -
> {noformat}
> Aishwarya-Gunes-MBP13:kafka aishwarya.gune$ ./bin/kafka-configs.sh
> --bootstrap-server localhost:9092 --alter --add-config
> 'log.cleaner.threads=2,log.cleaner.threads.config=30' --entity-default
> --entity-type brokers
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
