kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6166) Streams configuration requires consumer. and producer. in order to be read
Date Tue, 30 Jan 2018 18:56:00 GMT

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

ASF GitHub Bot commented on KAFKA-6166:
---------------------------------------

guozhangwang opened a new pull request #4489: KAFKA-6166: Update javadoc for streams config
URL: https://github.com/apache/kafka/pull/4489
 
 
   This PR piggy-back a few different javadoc changes:
   
   1. KIP-220: add admin client prefix.
   2. Clarify on user customized configs.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Assignee: Filipe Agapito
>            Priority: Minor
>              Labels: newbie++, user-experience
>             Fix For: 1.1.0, 1.0.1
>
>
> 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
(v7.6.3#76005)

Mime
View raw message