[SPARK-51489][SQL]Represent SQL scripts in Spark UI #52286
+126
−24
Conversation
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
miland-db
approved these changes
Sep 9, 2025
dusantism-db
commented
Sep 9, 2025
davidm-db
approved these changes
Sep 11, 2025
dusantism-db
force-pushed
the
spark-ui-scripting
branch
from
1c5e878 to
ee20063
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
This PR introduces support for SQL Scripts in the Spark UI. A "SQL Script ID" sortable column is introduced in the All Executions table in
SQL / Dataframetab of Spark UI. The column is only shown if there is at least one statement which has been executed by a script. Also, it introduces a SQL Script ID label in the single SQL Execution page, which is only present if the SQL Execution is executed by a script.A
sqlScriptIdis introduced for this purpose. It is an identifier which is unique per script execution. All statements within a single script execution will have the samesqlScriptId.Why are the changes needed?
Does this PR introduce any user-facing change?
Yes, Spark UI is expanded to show SQL Scripting information.
How was this patch tested?
Unit test added for script id.
UI changes manually - screenshots below.
SQL / Dataframe tab before running script (unchanged):
SQL / Dataframe tab after running two scripts with two statements each:
Single execution page:
Was this patch authored or co-authored using generative AI tooling?
No.