flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Ewen <se...@apache.org>
Subject Too many log4j.properties files
Date Mon, 06 Apr 2015 19:01:45 GMT
Hi all!

I see that a lot of people are committing log4j.properties files in the
compile scope of various projects. By now, when you start a flink
application, you have multiple log4j.properties files in the classpath.

./flink-examples/flink-java-examples/src/main/resources/log4j.properties
./flink-runtime/src/main/resources/log4j.properties
./flink-staging/flink-tez/src/main/resources/log4j.properties

That is certainly not how it should be. There should be none in there, it
messes with all assumptions considering log configurations.

For tests, there are even more log config files in the classpath

./flink-staging/flink-streaming/flink-streaming-core/src/test/resources/log4j.properties
./flink-staging/flink-hbase/src/test/resources/log4j.properties
./flink-staging/flink-tachyon/src/test/resources/log4j.properties

Please remove these files and pay attention to not commit these files, they
make it hard for anyone to actually want to debug based on log output to
configure the logging.

Greetings,
Stephan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message