linhongliu-db opened a new pull request, #39268: URL: https://github.com/apache/spark/pull/39268
### What changes were proposed in this pull request? This PR proposes to group all sub-executions together in SQL UI if they belong to the same root execution. We can have some follow-up improvements after this PR: 1. Add links to SQL page and Job page to indicate the root execution ID. 2. Better handling for the root execution missing case (e.g. eviction due to retaining limit). In this PR, the sub-executions will be displayed ungrouped. This feature is controlled by conf `spark.ui.sql.group.sub.execution.enabled` and the default value is set to `true` ### Why are the changes needed? better user experience. In PR #39220, the CTAS query will trigger a sub-execution to perform the data insertion. But the current UI will display the two executions separately which may confuse the users. In addition, this change should also help the structured streaming cases ### Does this PR introduce _any_ user-facing change? TODO ### How was this patch tested? <!-- If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible. If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future. If tests were not added, please describe why they were not added and/or why it was difficult to add. If benchmark tests were added, please run the benchmarks in GitHub Actions for the consistent environment, and the instructions could accord to: https://spark.apache.org/developer-tools.html#github-workflow-benchmarks. --> -- 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]
