[
https://issues.apache.org/jira/browse/KAFKA-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519199#comment-17519199
]
Matthias J. Sax commented on KAFKA-7509:
----------------------------------------
Thanks for staying on top of this. The filtering code is a partial solution to
the problem. Also the prefixes like `producer.` et al: yes they help. Not sure
if they solve all issues. KAFKA-6793 actually illustrates the general problem
we tried to solve.
However, IIRC KAFKA-6793 in particular was triggered by `StreamsConfig#retries`
that we needed to pass though the admin client into `StreamsPartitionAssignor`.
`StreamConfig#retries` was deprecated (it's still in the code, but unused and
not set on the `AdiminConfig` any longer) via KIP-572
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-572%3A+Improve+timeouts+and+retries+in+Kafka+Streams|https://cwiki.apache.org/confluence/display/KAFKA/KIP-572%3A+Improve+timeouts+and+retries+in+Kafka+Streams(]
-- thus, KAFKA-6793 might effectively resolved as a side effect, but only
because we stopped passing in an unrecognized config – thus, the underlying
principle issue is still there.
> 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: Chris Egerton
> 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
(v8.20.1#820001)
