You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 05:35:33 UTC

[jira] [Updated] (SPARK-2913) Spark's log4j.properties should always appear ahead of Hadoop's on classpath

     [ https://issues.apache.org/jira/browse/SPARK-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon updated SPARK-2913:
--------------------------------
    Labels: bulk-closed  (was: )

> Spark's log4j.properties should always appear ahead of Hadoop's on classpath
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-2913
>                 URL: https://issues.apache.org/jira/browse/SPARK-2913
>             Project: Spark
>          Issue Type: Bug
>          Components: Deploy
>    Affects Versions: 1.0.0, 1.0.2, 1.1.0
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>            Priority: Major
>              Labels: bulk-closed
>
> In the current {{compute-classpath}} scripts, the Hadoop conf directory may appear before Spark's conf directory in the computed classpath.  This leads to Hadoop's log4j.properties being used instead of Spark's, preventing users from easily changing Spark's logging settings.
> To fix this, we should add a new classpath entry for Spark's log4j.properties file.



--
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