Uh oh!
There was an error while loading. Please reload this page.
[SPARK-16808][Core] History Server main page does not honor APPLICATION_WEB_PROXY_BASE - #15855
Closed
vijoshi wants to merge 1 commit into
Closed
[SPARK-16808][Core] History Server main page does not honor APPLICATION_WEB_PROXY_BASE #15855vijoshi wants to merge 1 commit into
vijoshi wants to merge 1 commit into
Conversation
…ON_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 <vijoshi5@in.ibm.com>
SparkQA
commented
Nov 12, 2016
Test build #68540 has finished for PR 15855 at commit
|
vijoshi
commented
Nov 15, 2016
ContributorAuthor
@vanzin - ping |
vanzin
commented
Nov 15, 2016
Contributor
Merging to branch-2.0. |
asfgit pushed a commit
that referenced
this pull request
Nov 15, 2016
…ON_WEB_PROXY_BASE ## What changes were proposed in this pull request? Backport SPARK-16808 (#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. Author: Vinayak <vijoshi5@in.ibm.com> Closes#15855 from vijoshi/SPARK-16808_branch-2.0.
vanzin
commented
Nov 15, 2016
Contributor
@vijoshi could you close this? The bot doesn't do it for non-master PRs. |
vijoshi
commented
Nov 16, 2016
ContributorAuthor
Thanks @vanzin ! Closed the PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Backport SPARK-16808 (#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.