Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3009#issuecomment-63883863
Regarding "phantom" stages that are skipped:
What do you think about adding a "skipped" state to visually convey that
there were stage dependencies that _might_ have been computed but which were
skipped because their output was already available? Until a job completes, we
don't know for sure whether we'll need to go back and re-compute a stage that
was initially skipped, but after the job has completed the outcome will never
change.
We could add a "Skipped" stages section to the job details page.
On the "all jobs" page, we could display `(x skipped)` in the progress
bar/cell labels while advancing the bar to 100%, similar to what we do for
failed tasks.
How does this sound? Is this more/less confusing than the current behavior?
---
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
