-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-29053][WEBUI][2.4] Sort does not work on some columns #25882
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
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**  Closes apache#25855 from amanomer/SPARK29053. Authored-by: aman_omer <[email protected]> Signed-off-by: Sean Owen <[email protected]>
|
cc @srowen |
|
ok to test |
|
Test build #111121 has finished for PR 25882 at commit
|
|
@amanomer Could you rename PR title to |
|
Thanks @wangyum |
|
@amanomer Please add |
|
Test build #111157 has finished for PR 25882 at commit
|
|
@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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll review #25892 now and merge it soon. And, +1 for backporting separately.
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.
This reverts commit f788acf.
|
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 93ac4e1 Closes #25882 from amanomer/BP29053. Authored-by: aman_omer <[email protected]> Signed-off-by: Sean Owen <[email protected]>
|
Merged to 2.4 |
|
Thank you @srowen |
|
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