Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/246#issuecomment-39128529
It seems like there are two things at play here:
(1) Adding a cancel button in the UI. It sounds like this can be done in a
not-hugely-invasive way by adding a cancelStage() method in the DAGScheduler
that can be called by the UI.
(2) Adding job-level information to the UI. When we do this we might want
to rearrange how the cancellation gets implemented -- probably there will need
to be a refactoring of how the DAGScheduler keeps track of job / stage
information so that it can easily be shared with the UI (and at this point we
might want to move how the cancelStage() stuff happens).
I'd guess (1) can easily be done for 1.0 but (2) may not be able to be and
involves much larger changes. Seems fine for Sundeep to finish (1) here and
then @andrewor14 / @tdas / @pwendell to implement (2) later/separately?
---
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.
---
