[
https://issues.apache.org/jira/browse/KAFKA-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aishwarya Gune updated KAFKA-9593:
----------------------------------
Description:
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}
`./bin/kafka-configs.sh --bootstrap-server localhost:9092 --alter --add-config
'log.cleaner.threads.config=50' --entity-default --entity-type brokers`
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 -
```All sensitive broker config entries must be specified for --alter, missing
entries: Set(log.cleaner.threads.config)```
One way to update this config now is to specify the incorrect config too -
```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```
was:
When using kafka-config script to update config, attempt to update a
non-existing config goes through. For example -
`./bin/kafka-configs.sh --bootstrap-server localhost:9092 --alter --add-config
'log.cleaner.threads.config=50' --entity-default --entity-type brokers`
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 -
```All sensitive broker config entries must be specified for --alter, missing
entries: Set(log.cleaner.threads.config)```
One way to update this config now is to specify the incorrect config too -
```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```
> 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}
> `./bin/kafka-configs.sh --bootstrap-server localhost:9092 --alter
> --add-config 'log.cleaner.threads.config=50' --entity-default --entity-type
> brokers`
> 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 -
> ```All sensitive broker config entries must be specified for --alter, missing
> entries: Set(log.cleaner.threads.config)```
> One way to update this config now is to specify the incorrect config too -
> ```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```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
