You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/03/16 12:57:38 UTC

[jira] [Updated] (SPARK-6305) Add support for log4j 2.x to Spark

     [ https://issues.apache.org/jira/browse/SPARK-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen updated SPARK-6305:
-----------------------------
            Priority: Minor  (was: Major)
    Target Version/s: 2+
          Issue Type: Improvement  (was: New Feature)

I'm going to consider this targeted for Spark 2.x, when log4j can just be updated to 2.x (or not used).

That's good to hear, since it's a sticky problem. I suppose this worked, while userClassPathFirst doesn't, since this actually affects Spark's classpath and that is where the log4j 2 classes need to end up here.

I can still sort of imagine that Spark could use log4j 2 + 1.2-to-2 bridge, and update its config for log4j 2, and then require users to configure using 2.x syntax instead of 1.2 even if they use log4j 1.2. That's still not un-disruptive though. I wish it would just also support old syntax in that bridge!

> Add support for log4j 2.x to Spark
> ----------------------------------
>
>                 Key: SPARK-6305
>                 URL: https://issues.apache.org/jira/browse/SPARK-6305
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Tal Sliwowicz
>            Priority: Minor
>
> log4j 2 requires replacing the slf4j binding and adding the log4j jars in the classpath. Since there are shaded jars, it must be done during the build.



--
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