Page History

...

This change would impact any clients which were be working around the current buggy behaviour.

Reusing the previous example, after broker was upgraded to a version with this KIP implemented, kafka.foo.bar would appear to change from INFO to TRACE "on its own", without a user having explicitly reconfigured it. However, the level at which it was actually logging would remain TRACE both before and after upgrade. 

If this KIP were accepted for Kafka 3.0 then it would be less surprising to those clients.

...