[
https://issues.apache.org/jira/browse/SPARK-13793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated SPARK-13793:
------------------------------
Assignee: Tejas Patil
> PipedRDD doesn't propagate exceptions while reading parent RDDd
> ---------------------------------------------------------------
>
> Key: SPARK-13793
> URL: https://issues.apache.org/jira/browse/SPARK-13793
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.6.0
> Reporter: Tejas Patil
> Assignee: Tejas Patil
> Priority: Minor
> Fix For: 2.0.0
>
>
> PipeRDD creates a process to run the command and spawns a thread to feed the
> input data to the process's stdin. If there is any exception in the child
> thread which gets the input data from the parent RDD, the child thread does
> not propagate that exception to the main thread. eg. In event of fetch
> failures, since the exception is not be propagated, the entire stage fails.
> The correct behaviour would be to recompute the parent(s) and then relaunch
> the stage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
