[
https://issues.apache.org/jira/browse/KAFKA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375381#comment-15375381
]
Guozhang Wang commented on KAFKA-3929:
--------------------------------------
I am sorry for the late reply, missed your response in my email notifier..
Yeah that is the purpose. In the first step of KAFKA-3740 [~h...@pinterest.com]
already add the function to expose all config properties in key-value pairs
with sth. like {{ProcessorContext.appConfigsWithPrefix}}. And in this ticket we
just want make a standard set of prefixes that the library is aware of, and
also the users should obey when specifying the configs before constructing the
instance.
> Add prefix for underlying clients configs in StreamConfig
> ---------------------------------------------------------
>
> Key: KAFKA-3929
> URL: https://issues.apache.org/jira/browse/KAFKA-3929
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Ishita Mandhan
> Labels: api
>
> There are a couple of configs that have the same name for producer / consumer
> configs, e.g. take a look at {{CommonClientConfigs}}, and also for producer /
> consumer interceptors there are commonly named configs as well.
> This is semi-related to KAFKA-3740 since we need to add "sub-class" configs
> for RocksDB as well, and we'd better have some prefix mechanism for such
> hierarchical configs in general.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
