[jira] [Commented] (KAFKA-2939) Make AbstractConfig.logUnused() tunable for clients

["Jay Kreps (JIRA)" <ji...@apache.org>]

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

Jay Kreps commented on KAFKA-2939:
----------------------------------

That was the whole point of the original implementation. Looking at it now some weird stuff has been done. But the idea was that you have a config class that tracks access to the configs and that way even if there are custom configs defined in a serializer their use should get recorded and they shouldn't get logged as unused.

> Make AbstractConfig.logUnused() tunable for clients
> ---------------------------------------------------
>
>                 Key: KAFKA-2939
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2939
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>             Fix For: 0.9.1.0
>
>
> Today we always log unused configs in KafkaProducer / KafkaConsumer in their constructors, however for some cases like Kafka Streams that make use of these clients, other configs may be passed in to configure Partitioner / Serializer classes, etc. So it would be better to make this function call optional to avoid printing unnecessary and confusing WARN entries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)