Skip to content

Conversation

@guoxiaolongzte
Copy link

@guoxiaolongzte guoxiaolongzte commented Jan 10, 2018

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:
1

fix after:
2

How was this patch tested?

manual tests

Please review http://spark.apache.org/contributing.html before opening a pull request.

…have hidden and show features, when the table records very much.
@ajbozarth
Copy link
Member

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.

@guoxiaolongzte
Copy link
Author

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.
When so much data are loaded into the WEB UI, coupled with slow Internet access and other factors, if you have a hidden form of the function, not only for the overall look and feel of the WEB UI neat, more personal feel more convenient than jump access.
If you jump to a table and view the table's records, if you want to see the records in other tables, you have to flip it up and down because the jump's link is at the top of the page.
Attachment has been uploaded.

@srowen
Copy link
Member

srowen commented Jan 11, 2018

But @guoxiaolongzte your change doesn't cause it to load less data, right?

@guoxiaolongzte
Copy link
Author

No, just hide the table, in fact, the data is already on the page, but we can not see.
When we refresh the page, it will re-show all the data.

@ajbozarth
Copy link
Member

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

@guoxiaolongzte
Copy link
Author

guoxiaolongzte commented Jan 12, 2018

3

I'm going to achieve it, this is a good idea.

@guoxiaolongzte
Copy link
Author

@ajbozarth @srowen
Fix the code, increase the arrow of the form page, maintain the consistency of the function.

after fix:
4
5
6
7
8

Copy link
Member

@ajbozarth ajbozarth left a 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:

  1. You should move the class and onClick from the h4 to a surrounding span
  2. In order for collapsible tables to persist on reload each table much be added to the function at the bottom on web.js which 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.

@guoxiaolongzte
Copy link
Author

  1. The first suggestion, I will fix it.
  2. The second suggestion, I think it is not necessary. Because spark system is small, such as 3 workers, do not need to hide the table from the beginning.

@guoxiaolongzte
Copy link
Author

@ajbozarth
The first suggestion, I have already fixed it.
3

@ajbozarth
Copy link
Member

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.

@guoxiaolongzte
Copy link
Author

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.

@ajbozarth @srowen

@ajbozarth
Copy link
Member

LGTM now

@SparkQA
Copy link

SparkQA commented Jan 16, 2018

Test build #4055 has started for PR 20216 at commit 4b6cdbb.

@srowen
Copy link
Member

srowen commented Jan 16, 2018

This basically just makes the Workers / Apps lists collapsible in the same way as other blocks? that sounds fine.

@guoxiaolongzte
Copy link
Author

Yes, it makes the Workers / Apps lists collapsible in the same way as other blocks.

@guoxiaolongzte
Copy link
Author

test this please

@SparkQA
Copy link

SparkQA commented Jan 17, 2018

Test build #4056 has finished for PR 20216 at commit 4b6cdbb.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@guoxiaolongzte
Copy link
Author

guoxiaolongzte commented Jan 18, 2018

Please help merge code, thank you. @srowen

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Jan 19, 2018

Merged to master

@asfgit asfgit closed this in e1c33b6 Jan 19, 2018
asfgit pushed a commit that referenced this pull request Feb 13, 2018
…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:
![1](https://user-images.githubusercontent.com/26266482/36068644-df029328-0f14-11e8-8350-cfdde9733ffc.png)

## 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.
jackylee-ch pushed a commit to jackylee-ch/spark that referenced this pull request Feb 18, 2019
…, 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:**

![image](https://user-images.githubusercontent.com/23054875/46249137-f5c44880-c441-11e8-953a-a811e33ac24d.png)

**After fix:** Consistent with the other tabs.

![screenshot from 2018-09-30 00-11-28](https://user-images.githubusercontent.com/23054875/46249354-75074b80-c445-11e8-9417-28751fd8628a.png)

(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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants