[SPARK-53469][SQL] Ability to cleanup shuffle in Thrift server #52213
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
karuppayya
commented
Sep 3, 2025
| @@ -496,7 +496,8 @@ class SparkSession private( | |||
| parsedPlan | |||
| } | |||
| } | |||
| Dataset.ofRows(self, plan, tracker) | |||
| Dataset.ofRows(self, plan, tracker, | |||
There was a problem hiding this comment.
SparkExecuteStatementOperation's code eventually leads here.
|
cc: @cloud-fan |
HyukjinKwon
changed the title
added 2 commits
September 4, 2025 18:56
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?
We have the ability top clean up shuffle in
spark.sql.classic.shuffleDependency.fileCleanup.enabled.Honoring this in Thrift server and cleaning up shuffle.
Related PR comment here
Why are the changes needed?
This is to bring the behavior in par with other modes of sql execution(classic, connect)
Does this PR introduce any user-facing change?
No
How was this patch tested?
NA
Was this patch authored or co-authored using generative AI tooling?
No