spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-6305) Add support for log4j 2.x to Spark
Date Wed, 22 Aug 2018 19:57:00 GMT

    [ https://issues.apache.org/jira/browse/SPARK-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589303#comment-16589303
] 

Sean Owen commented on SPARK-6305:
----------------------------------

Ah, Java 9 is a good point. That may force the issue.

Yes you can accommodate some log4j 1.x uses on the classpath by slipping in the log4j 1 to
SLF4J shim as well. 

There's no way to control log levels in slf4j right? that is always delegated to the underlying
provider? I think a bit of that is unavoidable as some stuff in Spark wants to control logging.
Maybe it can be stripped down or centralized, sure.

Stuff in external/ would be treated the same way. It's meant to run with Spark. Some of those
modules like Flume might go away in Spark 3.

I think it will have to target Spark 3, but can target Spark 3.

 

> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message