[
https://issues.apache.org/jira/browse/SPARK-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327144#comment-16327144
]
Steve Loughran commented on SPARK-6305:
---------------------------------------
It'll be related to HADOOP-12956 , HDFS-12829, ZOOKEEPER-2342, and anything
else with the issue. Everything there needs to move off commons logging and
those tests which assume log4j underneath (log capture, mainly).
The fact that log4j2 doesn't work with log4j 1.x log4j.properties files has
meant there's no enthusiasm for moving to it for deployed services (breaks all
those management tools which manipulate the files), but that is no excuse for
the projects to block downstream apps from -> log4j2, as that's their
deployment problem. And, If Log4j 2.1 does handle .properties files, then life
is much simpler
If you get involved there, Hadoop 3.1 would be the milestone to aim for
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
