Turns out we shouldn't use logback because spark use slf4j-log4j12. During production, we will use the spark-submit command to submit cebes, therefore slf4j-log4j12 will be in the classpath, and slf4j will pick log4j anyway, regardless of us trying to use logback.
So we will stay with log4j. This PR also did some improvements on the log configuration:
Configure log4j in test time, separately for each module
Configure log4j in production time, with only cebes-http-server configured.
https://github.com/phvu/cebes-server/issues/52
Turns out we shouldn't use
logback
becausespark
useslf4j-log4j12
. During production, we will use thespark-submit
command to submit cebes, thereforeslf4j-log4j12
will be in the classpath, andslf4j
will picklog4j
anyway, regardless of us trying to uselogback
.So we will stay with
log4j
. This PR also did some improvements on the log configuration:cebes-http-server
configured.