Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14854
I thought of one significant UX improvement offered by the approach in this
withdrawn PR: when the current "multiple jobs" limit executes, there's no way
for the end user to know how much work remains in the worst case. If we do it
as one big job that we cancel midway through then the initial progress bar
displays the worst-case time estimate, helping the user to accurately determine
how long it might be to get all of the results (i.e. helps the user figure out
whether to go grab a cup of coffee or wait 20 seconds for things to finish).
/cc @marmbrus @rxin
---
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
