[
https://issues.apache.org/jira/browse/SPARK-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206162#comment-15206162
]
Sean Owen commented on SPARK-6305:
----------------------------------
I'm afraid I gave up and unfortunately lost my stashed attempt.
The pom changes are pretty horrible, since you have to exclude all log4j,
commons logging, slf4j bindings from all transitive dependencies, then add in
log4j, add in all the redirector dependencies to pipe log4j 1.2 et al to slf4j,
then from slf4j to log4 2.x. Most of the log4j-specific code needed non-trivial
overhauls, and I think I hit a snag there. The props files also don't work the
same way as before.
My conclusion was it wasn't worth it if it was just yet another way to log, and
stick to log4j 1.2.x, which is really tried and true. If there are performance
issues I wonder if we can isolate and improve them some other way?
> 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: [email protected]
For additional commands, e-mail: [email protected]
