Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-161062442
Updated patch. This does add a web UI filter, one which is being attached
to incomplete apps, and triggering checks of the underlying history, the goal
being when an updated account is reached, issue a 302 and then detach and
reattach the UI. Ideally, that will mean that on the next request the newly
loaded UI is picked up.
The test is failing. Currently because the fs history provider isn't
picking up the updated work. More investigations are needed. First step: adding
some sleeps in the test to guarantee the updated file has an updated timestamp
---
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
