GitHub user vijoshi opened a pull request:
https://github.com/apache/spark/pull/15855
[SPARK-16808][Core] History Server main page does not honor
APPLICATION_WEB_PROXY_BASE
## What changes were proposed in this pull request?
Backport SPARK-16808 (https://github.com/apache/spark/pull/15742) to
branch-2.0.
Application links generated on the history server UI no longer (regression
from 1.6) contain the configured spark.ui.proxyBase in the links. To address
this, made the uiRoot available globally to all javascripts for Web UI. Updated
the mustache template (historypage-template.html) to include the uiroot for
rendering links to the applications.
The existing test was not sufficient to verify the scenario where ajax call
is used to populate the application listing template, so added a new selenium
test case to cover this scenario.
## How was this patch tested?
Existing tests and a new unit test.
No visual changes to the UI.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vijoshi/spark SPARK-16808_branch-2.0
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/15855.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #15855
----
commit 844561cb5bb6127abec141eb073846dfb5aaa457
Author: Vinayak <[email protected]>
Date: 2016-11-09T18:40:14Z
[SPARK-16808][CORE] History Server main page does not honor
APPLICATION_WEB_PROXY_BASE
Application links generated on the history server UI no longer (regression
from 1.6) contain the configured spark.ui.proxyBase in the links. To address
this, made the uiRoot available globally to all javascripts for Web UI. Updated
the mustache template (historypage-template.html) to include the uiroot for
rendering links to the applications.
The existing test was not sufficient to verify the scenario where ajax call
is used to populate the application listing template, so added a new selenium
test case to cover this scenario.
Existing tests and a new unit test.
No visual changes to the UI.
Author: Vinayak <[email protected]>
----
---
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]
