-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-23024][WEB-UI]Spark ui about the contents of the form need to have hidden and show features, when the table records very much. #20216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…have hidden and show features, when the table records very much.
|
Since this is a UI change can you post screenshots, and I'm not 100% convinced on the necessity of this when we already have jump links at the top of most pages. |
|
Dear Sir, However, the real spark big data environment, a very large number of workers, every day running a very large number of applications, has completed a very large number of applications, there are also some failed applications. |
|
But @guoxiaolongzte your change doesn't cause it to load less data, right? |
|
No, just hide the table, in fact, the data is already on the page, but we can not see. |
|
Hiding Tables like this has been done elsewhere in the UI (can't remember where right now though). In that case there's a triangle marker next to the Header that shows that it's collapsable and it also persists across page load. If we decided to do this I think we should emulate that previous example |
…stency of the function.
|
@ajbozarth @srowen |
ajbozarth
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this is growing on me, it's actually pretty useful after all.
Looking at the previous example of aggregated-metrics in StagePage.scala I have a couple of code suggestions though:
- You should move the
classandonClickfrom theh4to a surroundingspan - In order for collapsible tables to persist on reload each table much be added to the function at the bottom on
web.jswhich I created with this possible future in mind. If you have a better suggestion for persistence though I'd love to hear it, mine is a bit brute force.
|
|
@ajbozarth |
|
Thanks for updating the first one, but I stand by the second. The UI should be consistent and in the previous use of this feature it persisted so it should here, even if it's not necessary every time. |
|
I agree with your second suggestion, before I did not understand what you mean, now I passed the test I understand what you mean. 1.In order for collapsible tables to persist on reload each table much be added to the function at the bottom on web.js. When I refresh the page, if it is hidden, will still be hidden; if it is displayed, will still be displayed. 2.to ensure user interface consistency. |
|
LGTM now |
|
Test build #4055 has started for PR 20216 at commit |
|
This basically just makes the Workers / Apps lists collapsible in the same way as other blocks? that sounds fine. |
|
Yes, it makes the Workers / Apps lists collapsible in the same way as other blocks. |
|
test this please |
|
Test build #4056 has finished for PR 20216 at commit
|
|
Please help merge code, thank you. @srowen |
|
Can one of the admins verify this patch? |
|
Merged to master |
…r need to have hidden and show features, when the table records very much. ## What changes were proposed in this pull request? Spark Streaming ui about the contents of the for need to have hidden and show features, when the table records very much. please refer to #20216 fix after:  ## How was this patch tested? (Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests) (If this patch involves UI changes, please attach a screenshot; otherwise, remove this) Please review http://spark.apache.org/contributing.html before opening a pull request. Author: guoxiaolong <guo.xiaolong1@zte.com.cn> Closes #20570 from guoxiaolongzte/SPARK-23382.
…, to make it consistent with other tabs. ## What changes were proposed in this pull request? Currently, SQL tab in the WEBUI doesn't support hiding table. Other tabs in the web ui like, Jobs, stages etc supports hiding table (refer SPARK-23024 apache#20216). In this PR, added the support for hide table in the sql tab also. ## How was this patch tested? bin/spark-shell ``` sql("create table a (id int)") for(i <- 1 to 100) sql(s"insert into a values ($i)") ``` Open SQL tab in the web UI **Before fix:**  **After fix:** Consistent with the other tabs.  (Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests) (If this patch involves UI changes, please attach a screenshot; otherwise, remove this) Please review http://spark.apache.org/contributing.html before opening a pull request. Closes apache#22592 from shahidki31/SPARK-25575. Authored-by: Shahid <shahidki31@gmail.com> Signed-off-by: Sean Owen <sean.owen@databricks.com>







What changes were proposed in this pull request?
Spark ui about the contents of the form need to have hidden and show features, when the table records very much. Because sometimes you do not care about the record of the table, you just want to see the contents of the next table, but you have to scroll the scroll bar for a long time to see the contents of the next table.
Currently we have about 500 workers, but I just wanted to see the logs for the running applications table. I had to scroll through the scroll bars for a long time to see the logs for the running applications table.
In order to ensure functional consistency, I modified the Master Page, Worker Page, Job Page, Stage Page, Task Page, Configuration Page, Storage Page, Pool Page.
fix before:

fix after:

How was this patch tested?
manual tests
Please review http://spark.apache.org/contributing.html before opening a pull request.