[
https://issues.apache.org/jira/browse/SPARK-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938467#comment-16938467
]
Rajiv Bandi edited comment on SPARK-6305 at 9/26/19 10:20 AM:
--------------------------------------------------------------
Steve, apart from the security issue concern, we also have the logs not rolling
properly.
In any case, my question is "Is Spark going to decouple itself from log4j 1.x
and provide a way to configure logging with an alternative implementation?".
If yes, what would be the tentative timeline?
was (Author: rajivbandi):
Steve, apart from the security issue concern, we also have the logs not rolling
properly.
In any case, my question is "Is Spark going to decouple itself from log4j 1.x
and provided a way to configure logging with an alternative implementation?".
If yes, what would be the tentative timeline?
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
