You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/07/06 08:19:11 UTC
[jira] [Resolved] (SPARK-16339) ScriptTransform does not print
stderr when outstream is lost
[ https://issues.apache.org/jira/browse/SPARK-16339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-16339.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0.1
Issue resolved by pull request 13834
[https://github.com/apache/spark/pull/13834]
> 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
> Fix For: 2.0.1
>
>
> 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