[SPARK-51548][SQL] Provides configuration to decide whether to copy objects before shuffle. #50318
Conversation
This file contains 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
…bjects before shuffle.
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?
Provides configuration to decide whether to copy objects before shuffle
Why are the changes needed?
For SparkSQL, We will decide whether to copy the object based on the type of shuffle writer. However, for some third-party shuffle writers, the object will be forced to be copied. However, sometimes it is unnecessary. For example, the shuffle writer in uniffle will directly serialize the record when processing each record, so it is also unnecessary.
Does this PR introduce any user-facing change?
Add new configuration
spark.sql.needToCopyObjectBeforeShuffleto enable or disable copy object before shuffle if the ShuffleManager is not SortShuffleManager.How was this patch tested?
No need to test.
Was this patch authored or co-authored using generative AI tooling?
No