Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/4891
Concerning loggers: I think for logging frameworks, they should rarely
bleed through, but if you instantiate multiple ones, you get problems. It is
more serious for the logging backend (where having multiple ones may mean
logging does not happen at all or get at least crazy warnings), but preventing
duplication in the logging frontend cannot hurt I believe.
Regarding non-primitive config options: Nice idea, but I would suggest to
do it without for now, because it does not seem crucial enough for me to slow
down a release for that.
How about configuring the default parent first options as:
`java.;org.apache.flink.;javax.annotation;org.slf4j;org.apache.log4j;org.apache.logging.log4j;ch.qos.logback`
---
