Hi, Indeed changing log level to debug would be the easiest and I think that would be a good solution. When no one object I'm ready to move forward with this approach and submit a MR.
The only minor thing I have – having it at debug log level might make it a bit less friendly for developers, especially for those who just do the first steps in Kafka. For example, if you misspelled the property name and trying to understand why things don't do what you expect. Having a warning might save some time in this case. Other than that I cannot see any reasons to have warnings there. Thanks, Artur On Thu, Dec 26, 2019 at 10:01 PM John Roesler <vvcep...@apache.org> wrote: > > Thanks for the KIP, Artur! > > For reference, here is the kip: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-552%3A+Add+interface+to+handle+unused+config > > I agree, these warnings are kind of a nuisance. Would it be feasible just to > leverage log4j in some way to make it easy to filter these messages? For > example, we could move those warnings to debug level, or even use a separate > logger for them. > > Thanks for starting the discussion. > -John > > On Tue, Dec 24, 2019, at 07:23, Artur Burtsev wrote: > > Hi, > > > > This KIP provides a way to deal with a warning "The configuration {} > > was supplied but isn't a known config." when it is not relevant. > > > > Cheers, > > Artur > >
