[SPARK-52486][SQL] Fix Spark Driver Planning OOM issue before Execution when enabling AQE #51184
+2
−2
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
…on when enabling AQE
|
HI @cloud-fan @MaxGekk @dongjoon-hyun Please give a review. |
There was a problem hiding this comment.
Thank you for making a PR, @zhixingheyi-tian . I have two comments.
- Please provide a reproducible example to clarify and validate your claim.
- Please revise the PR title more specifically because the current title is misleading because OOM depends on the situation. Technically, this PR cannot prevent all kind of Driver Planning OOM, right?
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?
Before generating SubQuery Physical Plans, we need to filtering dynamicpruning expression which is not worthwhile.
Why are the changes needed?
During the join operations of a dozen partitioned fact tables in Spark-SQL, 8w+ subqueries were generated, ultimately causing a Driver OOM (Out-Of-Memory) error.
How was this patch tested?
Existing Unit Tests can cover this PR.