GitHub user vanzin opened a pull request:

    https://github.com/apache/spark/pull/9816

    [RFC] [core] Make the repl log4j configuration override the root logger.

    In the default Spark distribution, there are currently two separate
    log4j config files, with different default values for the root logger,
    so that when running the shell you have a different default log level.
    This makes the shell more usable, since the logs don't overwhelm the
    output.
    
    But if you install a custom log4j.properties, you lose that, because
    then it's going to be used no matter whether you're running a regular
    app or the shell.
    
    With this change, the overriding of the log level is done differently;
    the log level repl's main class (org.apache.spark.repl.Main) is used
    to define the root logger's level when running the shell, defaulting
    to WARN if it's not set explicitly.
    
    On a somewhat related change, the shell output about the "sc" variable
    was changed a bit to contain a little more useful information about
    the application, since when the root logger's log level is WARN, that
    information is never shown to the user.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vanzin/spark shell-logging

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/9816.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #9816
    
----
commit 1df1ccdf0d507dbb4300746744abadb34e25c570
Author: Marcelo Vanzin <[email protected]>
Date:   2015-11-18T19:40:17Z

    [core] Make the repl log4j configuration override the root logger.
    
    In the default Spark distribution, there are currently two separate
    log4j config files, with different default values for the root logger,
    so that when running the shell you have a different default log level.
    This makes the shell more usable, since the logs don't overwhelm the
    output.
    
    But if you install a custom log4j.properties, you lose that, because
    then it's going to be used no matter whether you're running a regular
    app or the shell.
    
    With this change, the overriding of the log level is done differently;
    the log level repl's main class (org.apache.spark.repl.Main) is used
    to define the root logger's level when running the shell, defaulting
    to WARN if it's not set explicitly.
    
    On a somewhat related change, the shell output about the "sc" variable
    was changed a bit to contain a little more useful information about
    the application, since when the root logger's log level is WARN, that
    information is never shown to the user.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to