GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/675
[SPARK-1745] Move interrupted flag from TaskContext constructor
It makes little sense to start a TaskContext that is interrupted. Indeed, I
searched for all use cases of it and didn't find a single instance in which
interrupted is true on construction.
(This was inspired by reviewing #640, which adds an additional `@volatile
var completed` that is similar)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewor14/spark task-context
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/675.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 #675
----
commit 85311f86d4d929732289181a515e9d1a571019a2
Author: Andrew Or <[email protected]>
Date: 2014-05-07T03:36:16Z
Move interrupted flag from TaskContext constructor
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
