[
https://issues.apache.org/jira/browse/KAFKA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203958#comment-15203958
]
Ismael Juma commented on KAFKA-2939:
------------------------------------
The current code works as expected, but it could be improved to handle the case
where a higher-level component (eg Streams) is using lower-level clients
(KafkaConsumer/KafkaProducer) and wants to report unused configs once instead
of multiple times. To achieve this, we could:
* Pass a boolean to `AbstractConfig` that would silence
`AbstractConfig.logUnused` (or log at a `debug`/`trace` instead of `warn`)
* Make sure all producer and consumer usages would be recorded in the
StreamsConfig so that unused configs would be reported at that level
Given that Streams has a workaround at the moment (it removes its own configs
before passing them to the clients), moving this to 0.10.1.0.
> 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)
