spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Spark (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (SPARK-16339) ScriptTransform does not print stderr when outstream is lost
Date Fri, 01 Jul 2016 06:12:11 GMT

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

Apache Spark reassigned SPARK-16339:
------------------------------------

    Assignee:     (was: Apache Spark)

> ScriptTransform does not print stderr when outstream is lost
> ------------------------------------------------------------
>
>                 Key: SPARK-16339
>                 URL: https://issues.apache.org/jira/browse/SPARK-16339
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.6.2
>            Reporter: Tejas Patil
>            Priority: Trivial
>
> Currently, if due to some failure, the `outstream` gets destroyed or closed and later
`outstream.close()` leads to `IOException` in such case : https://github.com/apache/spark/blob/4f869f88ee96fa57be79f972f218111b6feac67f/sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/ScriptTransformation.scala#L325
> Due to this, the `stderrBuffer` does not get logged and there is no way for users to
see why the job failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message