t; messages can try to
> >>>>>> pinpoint
> >>>>>>>> where exactly the rogue configs are coming from?
> >>>>>>>>
> >>>>>>>> I might have overlooked a message at some point, but
>
gt;
> >
> > I wonder if other people know what the motivation behind the WARN log was?
> > I'm struggling to think up of a scenario where I'd like to see unused
> > values printed in anything above DEBUG.
> >
> >
> >
> > Best,
> > Stani
.
>
> Best,
> Stanislav
>
> On Mon, Dec 30, 2019 at 12:52 PM Artur Burtsev wrote:
>
> > Hi,
> >
> > Indeed changing the log level for the whole AbstractConfig is not an
> > option, because logAll is extremely useful.
> >
> > Grouping warnings int
e to be printed by default, and
> > anyone could disable it by setting
> > "org.apache.kafka.clients.producer.ProducerConfig.unused" to ERROR or OFF,
> > without disturbing the rest of the config log messages.
> >
> > It's simpler without the extra logge
ance. 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 T
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
; wrote:
> Hi Artur,>
>
> Can you let us know the id of your wiki account? Then, we can grant you
> permission.>
>
> Thanks,>
> -John>
>
> On Mon, Dec 16, 2019, at 10:09, Artur Burtsev wrote:>
> > Hi,>
> > >
> > I would like to fix t
Hi,
I would like to fix the
https://issues.apache.org/jira/browse/KAFKA-6793. Can you please grant
me permission, so I can submit KIP.
Thanks,
Artur
