[SPARK-51519][SQL] MERGE INTO/UPDATE/DELETE support join hint #50524
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
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?
This PR aims to make MERGE INTO/UPDATE/DELETE support join hint.
Why are the changes needed?
This feature request aims to enhance Spark SQL by adding support for join hints in
MERGE INTO,UPDATE, andDELETEoperations. Join hints can help optimize query execution by providing the Spark SQL engine with additional information about how to perform joins more efficiently. This improvement will allow users to specify join strategies (e.g., broadcast, shuffle) directly within these operations, leading to potentially significant performance gains in large-scale data processing scenarios.Does this PR introduce any user-facing change?
'No'.
Just inner change.
How was this patch tested?
GA.
Was this patch authored or co-authored using generative AI tooling?
'No'.