[SPARK-53652][SQL]Codegen for MergeRowExec #52399
Open
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
|
@aokolnychyi @rdblue @szehon-ho @cloud-fan @huaxingao @sunchao Can you help review this? |
karuppayya
force-pushed
the
SPARK-53652
branch
from
c0daaac to
8285941
Compare
|
@aokolnychyi @cloud-fan @dongjoon-hyun @rdblue Could one of you please help review this PR? This change specifically improves MERGE INTO operations by fusing the Join Operator (typically SortMerge) and the MergeRow operator. This fusion is expected to significantly boost MERGE performance at scale by reducing virtual function call overhead. Furthermore, it enables this path to be code-generated and potentially interoperate with other codegen-supported operators(most operators in Spark) in the future. |
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?
Generate code for MergeRowsExec operator
Why are the changes needed?
This would help operator fusing and improve performance of
MERGEoperationsDoes this PR introduce any user-facing change?
No
How was this patch tested?
All existing MergeRowsExec tests pass with codegen
Was this patch authored or co-authored using generative AI tooling?
No