[
https://issues.apache.org/jira/browse/KAFKA-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672356#comment-16672356
]
Matthias J. Sax commented on KAFKA-7509:
----------------------------------------
While logging in DEBUG level would prevent miss leading WARN log entries, it
seems to defeat the purpose, that is to guard against typing mistakes in
properties files etc. (ie, when plain strings instead of predefined const
values are used). Thus, I am not 100% convinced of this solution.
Thinking about this, we could instead define a prefix, that is use for all
configs that should be passed through. For all configs with this prefix, no
name check is done, and the prefix is stripped before it's passed into the
internal call to `configure()`. For example, Kafka Streams would not set
`admin.retries`, but `passthrough.admin.retries` avoiding the WARN log. (I hope
we find a better name than "passthrough" :) )
This would be a public API change though and require a KIP. Thoughts?
> Kafka Connect logs unnecessary warnings about unused configurations
> -------------------------------------------------------------------
>
> Key: KAFKA-7509
> URL: https://issues.apache.org/jira/browse/KAFKA-7509
> Project: Kafka
> Issue Type: Improvement
> Components: clients, KafkaConnect
> Affects Versions: 0.10.2.0
> Reporter: Randall Hauch
> Assignee: Randall Hauch
> Priority: Major
>
> When running Connect, the logs contain quite a few warnings about "The
> configuration '{}' was supplied but isn't a known config." This occurs when
> Connect creates producers, consumers, and admin clients, because the
> AbstractConfig is logging unused configuration properties upon construction.
> It's complicated by the fact that the Producer, Consumer, and AdminClient all
> create their own AbstractConfig instances within the constructor, so we can't
> even call its {{ignore(String key)}} method.
> See also KAFKA-6793 for a similar issue with Streams.
> There are no arguments in the Producer, Consumer, or AdminClient constructors
> to control whether the configs log these warnings, so a simpler workaround
> is to only pass those configuration properties to the Producer, Consumer, and
> AdminClient that the ProducerConfig, ConsumerConfig, and AdminClientConfig
> configdefs know about.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
