[SPARK-55971][UI] Add Jobs table to SQL execution detail page#54768
Closed
yaooqinn wants to merge 5 commits intoapache:masterfrom
Closed
[SPARK-55971][UI] Add Jobs table to SQL execution detail page#54768yaooqinn wants to merge 5 commits intoapache:masterfrom
yaooqinn wants to merge 5 commits intoapache:masterfrom
Conversation
Adds a collapsible 'Associated Jobs' table below Plan Details on the SQL execution detail page showing: Job ID (link), Status (badge), Duration, Stages (completed/total), Tasks (completed/total), and Description. Previously jobs were only shown as comma-separated ID links in the summary. Co-authored-by: Copilot <[email protected]>
- Use ApiHelper.lastStageNameAndDescription for description - Reverse sort order (newest job first) to match Jobs page - Add job detail link with stage name Co-authored-by: Copilot <[email protected]>
The visible progress label now shows just '(N killed)' instead of the full kill reason with stack trace. The full reason (truncated to 120 chars) is kept in the tooltip title for hover inspection. Co-authored-by: Copilot <[email protected]>
Add 'sortable' class to enable client-side column sorting via the existing sorttable.js library. Duration and Submitted columns use sorttable_customkey for correct numeric ordering. Stages and Tasks columns are marked sorttable_nosort since progress bars are not meaningfully sortable. Co-authored-by: Copilot <[email protected]>
- Catch only NoSuchElementException instead of all Exception - Wrap table in table-responsive div for small screens - Remove extra blank line left from jobLinks removal Co-authored-by: Copilot <[email protected]>
yaooqinn
changed the title
Member
Author
ScreenshotsSucceeded execution — Associated Jobs table (Exec 0): Failed execution with killed tasks — progress bar shows concise label (Exec 1): Full execution page showing table placement below Plan Details: Jobs page for style comparison: |
dongjoon-hyun
approved these changes
Mar 12, 2026
sarutak
approved these changes
Mar 13, 2026
Member
Author
|
Thank you @dongjoon-hyun @sarutak, merged to master |
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 free
to 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?
ApiHelper.lastStageNameAndDescription)Features:
sorttable.js(Stages/Tasks excluded withsorttable_nosort)NoSuchElementExceptioncatch)makeProgressBarvisible label now shows(N killed)instead of the full kill reason with stack trace. The truncated reason (120 chars) is kept in the tooltip for hover inspection. This applies globally across Jobs, Stages, and SQL execution pages.Why are the changes needed?
Previously jobs were shown as comma-separated ID links (e.g., "Running Jobs: 0 1 2") in the summary section, providing no context about job status, duration, or progress. The table shows all relevant information at a glance, matching the Jobs page style.
The progress bar kill reason text could be extremely long (full stack traces), making the bar unreadable.
Does this PR introduce any user-facing change?
Yes:
(N killed)instead of full error textHow was this patch tested?
Compilation verified. Manual testing with succeeded, failed, and killed-task jobs.
Was this patch authored or co-authored using generative AI tooling?
Yes, co-authored with GitHub Copilot.