[ https://issues.apache.org/jira/browse/KAFKA-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519748#comment-17519748 ]
Chris Egerton commented on KAFKA-7509: -------------------------------------- Thanks [~mjsax]. It seems like the root causes of this issue and KAFKA-6793 are actually quite different and, although we shouldn't implement a solution for one that is wholly incompatible with a solution for the other, it may not be necessary to address both at the same time. I'd be very curious to see if there's an example of a situation where it's unavoidable that unrecognized property warnings get logged by Kafka Streams, even when fully leveraging the namespacing mechanisms provided by the {{{}producer.{}}}, {{{}main.consumer.{}}}, etc. prefixes. I've updated [https://github.com/apache/kafka/pull/11986] to remove any changes to the public Java clients API, so it's ready for review if anyone wants to take a look. > 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)