[
https://issues.apache.org/jira/browse/KAFKA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210641#comment-15210641
]
Guozhang Wang commented on KAFKA-2939:
--------------------------------------
I feel that the second option, i.e. making sure all streams-specific usages
must be recorded before constructing producer and consumer clients are quite
hard to achieve in practice. Personally I would prefer either option 1) or have
easy way to construct producer / consumer configs from the high-level configs
(today this is the workaround in streams, where we have to enumerate
one-by-one).
> Make AbstractConfig.logUnused() tunable for clients
> ---------------------------------------------------
>
> Key: KAFKA-2939
> URL: https://issues.apache.org/jira/browse/KAFKA-2939
> Project: Kafka
> Issue Type: Improvement
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Labels: newbie
> Fix For: 0.10.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)
