GitHub user tejasapatil opened a pull request:
https://github.com/apache/spark/pull/11628
[SPARK-13793] [CORE] PipedRDD doesn't propagate exceptions while reading
parent RDD
## What changes were proposed in this pull request?
PipedRDD creates a child thread to read output of the parent stage and feed
it to the pipe process. Used a variable to save the exception thrown in the
child thread and then propagating the exception in the main thread if the
variable was set.
## How was this patch tested?
- Added a unit test
- Tested the patch with a real pipe() job, bounced the executor node which
ran the parent stage to simulate a fetch failure and observed that the parent
stage was re-ran.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tejasapatil/spark pipe_rdd
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/11628.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 #11628
----
commit 0a260a0609ae8364b9bb9c23d71ae8802f3a34cd
Author: Tejas Patil <tej...@fb.com>
Date: 2016-03-10T04:26:25Z
[SPARK-13793] [CORE] PipeRDD doesn't propagate exceptions while reading
parent RDD
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
