Uh oh!
There was an error while loading. Please reload this page.
[SPARK-29053][WEBUI][2.4] Sort does not work on some columns - #25882
[SPARK-29053][WEBUI][2.4] Sort does not work on some columns#25882amanomer wants to merge 3 commits into
Conversation
Setting custom sort key for duration and execution time column. Sorting on duration and execution time columns consider time as a string after converting into readable form which is the reason for wrong sort results as mentioned in [SPARK-29053](https://issues.apache.org/jira/browse/SPARK-29053). No Test manually. Screenshots are attached. After patch: **Duration**  **Execution time**  Closesapache#25855 from amanomer/SPARK29053. Authored-by: aman_omer <amanomer1996@gmail.com> Signed-off-by: Sean Owen <sean.owen@databricks.com>
amanomer
commented
Sep 21, 2019
cc @srowen |
HyukjinKwon
commented
Sep 21, 2019
ok to test |
SparkQA
commented
Sep 21, 2019
Test build #111121 has finished for PR 25882 at commit
|
wangyum
commented
Sep 22, 2019
@amanomer Could you rename PR title to |
amanomer
commented
Sep 22, 2019
Thanks @wangyum |
wangyum
commented
Sep 22, 2019
@amanomer Please add |
SparkQA
commented
Sep 22, 2019
Test build #111157 has finished for PR 25882 at commit
|
srowen
commented
Sep 22, 2019
@wangyum does this really address SPARK-28599? this seems to just sort the current page? which brings up an issue of whether that's confusing (or maybe I misunderstood). In any event, this one is just a back-port; does the original PR address it too? |
| <td>{info.groupId}</td> | ||
| <td>{formatDate(info.startTimestamp)}</td> | ||
| <td>{formatDate(info.finishTimestamp)}</td> | ||
| <td>{formatDurationOption(Some(info.totalTime))}</td> |
There was a problem hiding this comment.
@srowen This change to backport SPARK-28599.
Or we should revert this change and make another PR to make it clear?
There was a problem hiding this comment.
I see, these are really duplicates? I would first merge #25892 then, but, hm, how is it not a merge conflict? I'm missing something.
My larger point was: does this actually mean you sort all of the entries when there are many pages of them? or just the current page?
There was a problem hiding this comment.
Oh I see. Well, want to at least merge #25892 first and then include it here? we can back-port it separately, too.
There was a problem hiding this comment.
I'll review #25892 now and merge it soon. And, +1 for backporting separately.
This reverts commit f788acf.
amanomer
commented
Sep 22, 2019
SparkQA
commented
Sep 22, 2019
Test build #111167 has finished for PR 25882 at commit
|
### What changes were proposed in this pull request? Setting custom sort key for duration and execution time column. ### Why are the changes needed? Sorting on duration and execution time columns consider time as a string after converting into readable form which is the reason for wrong sort results as mentioned in [SPARK-29053](https://issues.apache.org/jira/browse/SPARK-29053). ### Does this PR introduce any user-facing change? No. ### How was this patch tested? Test manually. Back-port of commit 93ac4e1Closes#25882 from amanomer/BP29053. Authored-by: aman_omer <amanomer1996@gmail.com> Signed-off-by: Sean Owen <sean.owen@databricks.com>
srowen
commented
Sep 23, 2019
Merged to 2.4 |
amanomer
commented
Sep 23, 2019
Thank you @srowen |
dongjoon-hyun
commented
Sep 23, 2019
Thank you all! |
What changes were proposed in this pull request?
Setting custom sort key for duration and execution time column.
Why are the changes needed?
Sorting on duration and execution time columns consider time as a string after converting into readable form which is the reason for wrong sort results as mentioned in SPARK-29053.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Test manually.
Back-port of commit 93ac4e1