[ 
https://issues.apache.org/jira/browse/KAFKA-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516226#comment-17516226
 ] 

Chris Egerton commented on KAFKA-7509:
--------------------------------------

Alright, I dug a little deeper and it looks like this has been discussed in 
even greater detail in KAFKA-6793 and 
[KIP-552|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=142641934].
 The progress there stalled after the concept of the {{RecordingMap}} mechanism 
was brought up.

I think that that approach has some merit and have put together a proof of 
concept here: [https://github.com/apache/kafka/pull/11986]

This may still require a KIP (possibly just alterations to the existing 
KIP-552), but it's borderline.

[~mjsax] does it look like this same approach might work with Streams too?

> 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)

Reply via email to