diff options
author | Andrew Or <andrewor14@gmail.com> | 2014-05-08 12:13:07 -0700 |
---|---|---|
committer | Aaron Davidson <aaron@databricks.com> | 2014-05-08 12:13:07 -0700 |
commit | c3f8b78c211df6c5adae74f37e39fb55baeff723 (patch) | |
tree | aedc2a8c201e2d697080b405af9820f932f68ecf /examples | |
parent | 44dd57fb66bb676d753ad8d9757f9f4c03364113 (diff) | |
download | spark-c3f8b78c211df6c5adae74f37e39fb55baeff723.tar.gz spark-c3f8b78c211df6c5adae74f37e39fb55baeff723.tar.bz2 spark-c3f8b78c211df6c5adae74f37e39fb55baeff723.zip |
[SPARK-1745] Move interrupted flag from TaskContext constructor (minor)
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. These are not the most urgent changes, but I wanted to push them out before I forget.
Author: Andrew Or <andrewor14@gmail.com>
Closes #675 from andrewor14/task-context and squashes the following commits:
9575e02 [Andrew Or] Add space
69455d1 [Andrew Or] Merge branch 'master' of github.com:apache/spark into task-context
c471490 [Andrew Or] Oops, removed one flag too many. Adding it back.
85311f8 [Andrew Or] Move interrupted flag from TaskContext constructor
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions