[SPARK-53483][SQL] Support disable code-gen for sort merge join other than FULL OUTER and Existence #52227
+10
−2
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?
Support disable code-gen for sort merge join other than FULL OUTER and Existence. In addition, adjust the default value of spark.sql.sortMergeJoinExec.buffer.in.memory.threshold to be consistent with the BUFFER_IN_MEMORY_THRESHOLD of other operators, which is 4096.
Why are the changes needed?
Avoid executor OOM when a single key matches too many rows in inner/left outer/ right outer sort merge join beccause of currentRows.
Before pr, we can only increase the executor memory. After pr, we can disable code-gen for sort merge join.
Does this PR introduce any user-facing change?
Yes, new configuration
spark.sql.codegen.join.sortMergeJoin.enabled
.How was this patch tested?
Local test, before pr will OOM, after pr run successfully.
Was this patch authored or co-authored using generative AI tooling?
No.