XdithyX opened a new pull request, #56090:
URL: https://github.com/apache/spark/pull/56090

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://spark.apache.org/contributing.html
     2. Ensure you have added or run the appropriate tests for your PR: 
https://spark.apache.org/developer-tools.html
     3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP][SPARK-XXXX] Your PR title ...'.
     4. Be sure to keep the PR description updated to reflect all changes.
     5. Please write your PR title to summarize what this PR proposes.
     6. If possible, provide a concise example to reproduce the issue for a 
faster review.
     7. If you want to add a new configuration, please read the guideline first 
for naming configurations in
        
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
     8. If you want to add or modify an error type or message, please read the 
guideline first in
        'common/utils/src/main/resources/error/README.md'.
   -->
   
   ### What changes were proposed in this pull request?
   This PR adds a SQL workload summary table at the top of the SQL tab 
([SPARK-55876](https://issues.apache.org/jira/browse/SPARK-55876)).
   
   The summary is returned as part of the existing SQL table REST response and 
rendered above the SQL executions table. The UI follows the existing Spark UI 
table pattern used by the Executors page: the summary is rendered as a compact 
DataTable with paging, searching, ordering, and info disabled.
   
   The summary contains the following fields:
   
   - Total Queries: total number of SQL executions known to the SQL status 
store.
   - Average Duration: average duration across SQL executions. Completed and 
failed executions use their final duration. Running executions use their 
current elapsed duration, consistent with how the SQL executions table displays 
duration.
   - Running Queries: number of SQL executions whose current status is RUNNING.
   - Failed Queries: number of SQL executions whose current status is FAILED.
   - Failure Rate: failed queries divided by total queries, displayed as a 
percentage. When there are no queries, this is displayed as 0.0%.
   
   The SQL executions table remains unchanged functionally. 
   
   
   ### Why are the changes needed?
   The SQL tab currently requires users to inspect the full executions table to 
understand the overall SQL workload state.
   
   Adding a summary table provides an at-a-glance view of SQL workload health, 
including total query volume, average duration, currently running queries, and 
failure rate.
   
   
   ### Does this PR introduce _any_ user-facing change?
   Yes.
   
   The SQL / DataFrame tab now shows a Summary table above the SQL Executions 
table. The existing SQL executions table and status filter continue to work as 
before.
   
   
   
   ### How was this patch tested?
   Ran:
   
   - `build/sbt 'sql/testOnly 
org.apache.spark.status.api.v1.sql.SqlResourceWithActualMetricsSuite'`
   - `build/sbt 'sql/testOnly 
org.apache.spark.sql.execution.ui.AllExecutionsPageWithInMemoryStoreSuite'`
   
   
   ### Was this patch authored or co-authored using generative AI tooling?
   Generated-by: OpenAI Codex GPT 5.5
   
   ### Before
   <img width="1512" height="468" alt="before" 
src="https://github.com/user-attachments/assets/9bd28a2a-2af5-49a4-b6f0-9480cc6a8f01";
 />
   
   ### After
   <img width="1511" height="639" alt="Screenshot 2026-05-24 at 6 37 52 PM" 
src="https://github.com/user-attachments/assets/09c2b3b3-fe9c-4020-bbf6-f3c6720bc607";
 />
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to