[jira] [Created] (KAFKA-8592) Broker Dynamic Configuration fails to resolve variables as per KIP-421
TEJAL ADSUL created KAFKA-8592: -- Summary: Broker Dynamic Configuration fails to resolve variables as per KIP-421 Key: KAFKA-8592 URL: https://issues.apache.org/jira/browse/KAFKA-8592 Project: Kafka Issue Type: Bug Components: config Affects Versions: 2.3.0 Reporter: TEJAL ADSUL Fix For: 2.3.1 In add/alter new configs for DynamicConfigs it does not go through the KafkaConfig eg: bin/kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-name 0 --alter --add-config log.cleaner.threads=2 However the bootstrap-server localhost is parsed through the kafkaConfig to create the adminClient but not the log.cleaner.thread. As the configs are not parsed using the KafkaConfig if we pass variables in configs they are bot resolved at run time. In order to resolve the variables in alterConfig/addConfigs flow we need to parse the new configs using KafkaConfig before they are parsed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KAFKA-8426) KIP 421 Bug: ConfigProvider configs param inconsistent with KIP-297
TEJAL ADSUL created KAFKA-8426:
--
Summary: KIP 421 Bug: ConfigProvider configs param inconsistent
with KIP-297
Key: KAFKA-8426
URL: https://issues.apache.org/jira/browse/KAFKA-8426
Project: Kafka
Issue Type: Bug
Reporter: TEJAL ADSUL
Fix For: 2.3.0
According to KIP-297 a parameter is passed to ConfigProvider with syntax
"config.providers.\{name}.param.\{param-name}". Currently AbstractConfig allows
parameters of the format "config.providers.\{name}.\{param-name}". With this
fix AbstractConfig will be consistent with KIP-297 syntax.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KAFKA-8425) KIP 421 Bug: Modifying Immutable Originals Map results in Java exception
TEJAL ADSUL created KAFKA-8425: -- Summary: KIP 421 Bug: Modifying Immutable Originals Map results in Java exception Key: KAFKA-8425 URL: https://issues.apache.org/jira/browse/KAFKA-8425 Project: Kafka Issue Type: Bug Components: config Reporter: TEJAL ADSUL Fix For: 2.3.0 The originals map passed to the AbstractConfig class can be immutable. The resolveConfigVariable function was modifying the originals map. If this map is immutable it will result in an exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KAFKA-7847) KIP-421: Support resolving externalized secrets in AbstractConfig
TEJAL ADSUL created KAFKA-7847: -- Summary: KIP-421: Support resolving externalized secrets in AbstractConfig Key: KAFKA-7847 URL: https://issues.apache.org/jira/browse/KAFKA-7847 Project: Kafka Issue Type: Improvement Components: config Reporter: TEJAL ADSUL This proposal intends to enhance the AbstractConfig base class to support replacing variables in configurations just prior to parsing and validation. This simple change will make it very easy for client applications, Kafka Connect, and Kafka Streams to use shared code to easily incorporate externalized secrets and other variable replacements within their configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KAFKA-7846) KIP-421: Support resolving externalized secrets in AbstractConfig
TEJAL ADSUL created KAFKA-7846: -- Summary: KIP-421: Support resolving externalized secrets in AbstractConfig Key: KAFKA-7846 URL: https://issues.apache.org/jira/browse/KAFKA-7846 Project: Kafka Issue Type: Improvement Components: config Reporter: TEJAL ADSUL This proposal intends to enhance the AbstractConfig base class to support replacing variables in configurations just prior to parsing and validation. This simple change will make it very easy for client applications, Kafka Connect, and Kafka Streams to use shared code to easily incorporate externalized secrets and other variable replacements within their configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
