[jira] [Commented] (SPARK-4147) Remove log4j dependency

["Sean Owen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189739#comment-14189739 ] 

Sean Owen commented on SPARK-4147:
----------------------------------

Yes, slf4j does not let you actually control logging levels. You have to call into a specific logging implementation for this, and that's why log4j is used directly. You can re-route log4j to slf4j and slf4j to your own logger, still. I think this on purpose, so I don't necessarily think this should change. 

> Remove log4j dependency
> -----------------------
>
>                 Key: SPARK-4147
>                 URL: https://issues.apache.org/jira/browse/SPARK-4147
>             Project: Spark
>          Issue Type: Wish
>          Components: Spark Core
>    Affects Versions: 1.1.0
>            Reporter: Tobias Pfeiffer
>
> spark-core has a hard dependency on log4j, which shouldn't be necessary since slf4j is used. I tried to exclude slf4j-log4j12 and log4j dependencies in my sbt file.
> Excluding org.slf4j.slf4j-log4j12 works fine if logback is on the classpath. However, removing the log4j dependency fails because in https://github.com/apache/spark/blob/v1.1.0/core/src/main/scala/org/apache/spark/Logging.scala#L121 a static method of org.apache.log4j.LogManager is accessed *even if* log4j is not in use.
> I guess removing all dependencies on log4j may be a bigger task, but it would be a great help if the access to LogManager would be done only if log4j use was detected before. (This is a 2-line change.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org