[
https://issues.apache.org/jira/browse/SPARK-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938506#comment-16938506
]
Steve Loughran commented on SPARK-6305:
---------------------------------------
bq. Steve, apart from the security issue concern, we also have the logs not
rolling properly.
Are you confident that this is actually due to log4j 1.x bugs -and that an
upgrade Will make it go away? As if not, unless you can find evidence that
other people been finding a similar problem, I'd worry about your deployment
and configuration before that of the trauma of a move to 2.x
bq. 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?".
bq. If yes, what would be the tentative timeline?
No idea.
I actually seem to recall some discussion about using logback behind the
scenes, though you'll have to investigate that yourself
> 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: [email protected]
For additional commands, e-mail: [email protected]
