Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3009#issuecomment-63423908
Would there be an alternative approach where we keep a fixed goal post but
we risk "over estimating" the size of the job if there are stages that are, in
fact, not ever computed? We could either just have the job shown as "finished"
but not be 100% complete or we could simply advance the slider to 100% when the
job finishes (since jobs, thankfully, cannot be resubmitted once completed!).
My concern with abandoning the fixed goal post is that it's going to be
frustrating for users to think their job is close to finishing and then all of
a sudden the progress bar goes backwards. And this will happen fairly often
since many jobs in the wild have multiple stages.
I wonder if it would be better to make the UX "bad" for the relatively rare
case of shared stages than for the very common case of computed stages. And
it's only "bad" in that it under promises and then over-delivers on completion
time.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
