You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2015/06/11 08:10:00 UTC

[jira] [Updated] (KAFKA-2249) KafkaConfig does not preserve original Properties

     [ https://issues.apache.org/jira/browse/KAFKA-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gwen Shapira updated KAFKA-2249:
--------------------------------
    Attachment: KAFKA-2249.patch

> 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
>         Attachments: KAFKA-2249.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)