[ https://issues.apache.org/jira/browse/SPARK-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Wendell updated SPARK-5524: ----------------------------------- Component/s: Spark Core > Remove messy dependencies to log4j > ---------------------------------- > > Key: SPARK-5524 > URL: https://issues.apache.org/jira/browse/SPARK-5524 > Project: Spark > Issue Type: Task > Components: Spark Core > Reporter: Jacek Lewandowski > > There are some tickets regarding loosening the dependency on Log4j, however > some classes still use the following scheme: > {code} > if (Logger.getLogger(classOf[SomeClass]).getLevel == null) { > Logger.getLogger(classOf[SomeClass]).setLevel(someLevel) > } > {code} > This doesn't look good and make it difficult to track why some logs are > missing when you use Log4j and why they are flooding when you use something > else, like logback. > There is a Logging class which checks whether we use Log4j or not. Why not > delegate all of such invocations, where the Logging class could handle it > properly, maybe considering more logging implementations? -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org