[jira] [Commented] (KAFKA-6166) Streams configuration requires consumer. and producer. in order to be read

["Ted Yu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237846#comment-16237846 ] 

Ted Yu commented on KAFKA-6166:
-------------------------------

How about populating the first two configs with the value for custom-key-for-metric-reporter, by default ?

> Streams configuration requires consumer. and producer. in order to be read
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-6166
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6166
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.11.0.0
>         Environment: Kafka 0.11.0.0
> JDK 1.8
> CoreOS
>            Reporter: Justin Manchester
>            Priority: Minor
>
> Problem:
> In previous release you could specify a custom metrics reporter like so:
> Properties config = new Properties(); 
> config.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG, "kafka-broker1:9092"); 
> config.put(StreamsConfig.METRIC_REPORTER_CLASSES_CONFIG, "com.mycompany.MetricReporter"); 
> config.put("custom-key-for-metric-reporter", "value");
> From 0.11.0.0 onwards this is no longer possible, as you have to specify consumer.custom-key-for-metric-reporter or producer.custom-key-for-metric-reporter otherwise it's stripped out of the configuration.
> So, if you wish to use a metrics reporter and to collect producer and consumer metrics, as well as kafka-streams metrics, that you would need to specify 3 distinct configs:
> 1) consumer.custom-key-for-metric-reporter 
> 2) producer.custom-key-for-metric-reporter 
> 3) custom-key-for-metric-reporter
> This appears to be a regression.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)