You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2019/01/30 19:04:00 UTC

[jira] [Resolved] (SPARK-26753) Log4j customization not working for spark-shell

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

Marcelo Vanzin resolved SPARK-26753.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

Issue resolved by pull request 23675
[https://github.com/apache/spark/pull/23675]

> Log4j customization not working for spark-shell
> -----------------------------------------------
>
>                 Key: SPARK-26753
>                 URL: https://issues.apache.org/jira/browse/SPARK-26753
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 3.0.0
>            Reporter: Ankur Gupta
>            Assignee: Ankur Gupta
>            Priority: Major
>             Fix For: 3.0.0
>
>
> It's pretty common to add log4j entries to customize the level of specific loggers. e.g. adding the following to log4j.properties:
> {code:java}
> log4j.logger.org.apache.spark.deploy.security=DEBUG
> {code}
> This works fine on previous releases but not for the current build for spark-shell. This is probably caused by SPARK-25118.



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