[
https://issues.apache.org/jira/browse/KAFKA-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871773#comment-16871773
]
Patrik Kleindl commented on KAFKA-7509:
---------------------------------------
Not related to Connect but giving this a bump because of
[https://confluentcommunity.slack.com/archives/C48AHTCUQ/p1561063563237400],
maybe it will help get this moving again.
The warning happens in Kafka Streams on several occasions:
* admin.retries because this is passed from streams itself to the admin client
* when trying to override a property for e.g. main.consumer.max.poll.records
* when trying to pass a property through the application properties to the
RocksDBConfigSetter (they are added automatically there, but also produce
warnings)
The first two pop up because the prefixes are stripped from the properties when
they are used but not handled in the comparison.
And the code does not filter out properties based on the prefix if they are not
even aimed at the receiver (e.g. admin.retries should not affect the producer).
The third would qualify for the "passthrough" approach mentioned above.
> 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)
