[
https://issues.apache.org/jira/browse/SPARK-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409829#comment-15409829
]
Sean Owen commented on SPARK-6305:
----------------------------------
The problem, I think, is that then this would not take effect if the user
overrides with a custom logging configuration.
If this, or the silencing that some of the examples do, is really otherwise
blocking this change, I'd say yank it out so we can update and just live with
the message or provide at least the appropriate config in a default logging
file that users can copy if desired.
I'm not so so worried about this aspect as much as maintaining the right POM
configuration to exclude and continue to exclude all external usages of log4j 1
and do all the appropriate redirecting. That's going to be a small nightmare to
keep correct, though, if Spark stops using log4j directly, probably less
problematic.
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
