[
https://issues.apache.org/jira/browse/KAFKA-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reopened KAFKA-2249:
----------------------------
[~gwenshap], with this patch, an issue that I realized is that we print out the
configs in LogConfig for every partition. If there are lots of partitions in a
broker, the logging is too much. Perhaps we can add another constructor in
AbstractConfig to disable logging for LogConfig.
> KafkaConfig does not preserve original Properties
> -------------------------------------------------
>
> Key: KAFKA-2249
> URL: https://issues.apache.org/jira/browse/KAFKA-2249
> Project: Kafka
> Issue Type: Bug
> Reporter: Gwen Shapira
> Assignee: Gwen Shapira
> Fix For: 0.8.3
>
> Attachments: KAFKA-2249.patch, KAFKA-2249_2015-06-17_17:35:35.patch
>
>
> We typically generate configuration from properties objects (or maps).
> The old KafkaConfig, and the new ProducerConfig and ConsumerConfig all retain
> the original Properties object, which means that if the user specified
> properties that are not part of ConfigDef definitions, they are still
> accessible.
> This is important especially for MetricReporters where we want to allow users
> to pass arbitrary properties for the reporter.
> One way to support this is by having KafkaConfig implement AbstractConfig,
> which will give us other nice functionality too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
