spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Owen <so...@cloudera.com>
Subject Re: SparkSubmit.scala and stderr
Date Tue, 03 Feb 2015 21:56:05 GMT
Despite its name, stderr is frequently used as the destination for
anything that's not the output of the program, which includes log
messages. That way, for example, you can redirect the output of such a
program to capture its result without also capturing log or error
messages, which will still just print to the console.

On Tue, Feb 3, 2015 at 8:28 AM, jayhutfles <jayhutfles@gmail.com> wrote:
> Hi all,
>
> I just saw that the SparkSubmit.scala class has the following lines:
>
>   object SparkSubmit {
>     ...
>     // Exposed for testing
>     private[spark] var printStream: PrintStream = System.err
>     ...
>   }
>
> This causes all verbose logging messages elsewhere in SparkSubmit to go to
> stderr, not stdout.  Is this by design?  Verbose messages don't necessarily
> reflect errors.  But as the comment states that it's for testing, maybe I'm
> misunderstanding its intent...
>
> Thanks in advance
>   -Jay
>
>
>
> --
> View this message in context: http://apache-spark-developers-list.1001551.n3.nabble.com/SparkSubmit-scala-and-stderr-tp10417.html
> Sent from the Apache Spark Developers List mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
> For additional commands, e-mail: dev-help@spark.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
For additional commands, e-mail: dev-help@spark.apache.org


Mime
View raw message