-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-34514][SQL] Push down limit for LEFT SEMI and LEFT ANTI join #31630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4034,6 +4034,36 @@ class SQLQuerySuite extends QueryTest with SharedSparkSession with AdaptiveSpark | |
| checkAnswer(df, Row(0, 0) :: Row(0, 1) :: Row(0, 2) :: Nil) | ||
| } | ||
| } | ||
|
|
||
| test("SPARK-34514: Push down limit through LEFT SEMI and LEFT ANTI join") { | ||
| withTable("left_table", "nonempty_right_table", "empty_right_table") { | ||
| spark.range(5).toDF().repartition(1).write.saveAsTable("left_table") | ||
| spark.range(3).write.saveAsTable("nonempty_right_table") | ||
| spark.range(0).write.saveAsTable("empty_right_table") | ||
| Seq("LEFT SEMI").foreach { joinType => | ||
|
||
| val joinWithNonEmptyRightDf = spark.sql( | ||
| s"SELECT * FROM left_table $joinType JOIN nonempty_right_table LIMIT 3") | ||
| val joinWithEmptyRightDf = spark.sql( | ||
| s"SELECT * FROM left_table $joinType JOIN empty_right_table LIMIT 3") | ||
|
|
||
| Seq(joinWithNonEmptyRightDf, joinWithEmptyRightDf).foreach { df => | ||
| val pushedLocalLimits = df.queryExecution.optimizedPlan.collect { | ||
| case l @ LocalLimit(_, _: LogicalRelation) => l | ||
| } | ||
| assert(pushedLocalLimits.length === 1) | ||
| } | ||
|
|
||
| val expectedAnswer = Seq(Row(0), Row(1), Row(2)) | ||
| if (joinType == "LEFT SEMI") { | ||
| checkAnswer(joinWithNonEmptyRightDf, expectedAnswer) | ||
| checkAnswer(joinWithEmptyRightDf, Seq.empty) | ||
| } else { | ||
| checkAnswer(joinWithNonEmptyRightDf, Seq.empty) | ||
| checkAnswer(joinWithEmptyRightDf, expectedAnswer) | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
|
|
||
| case class Foo(bar: Option[String]) | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm, in this case, we need the join itself?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we still need. Whether to output all rows or nothing, is depending on whether right side is empty, and this can only be known during runtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maropu - this actually reminds me whether we can further optimize during runtime, and I found I already did it for LEFT SEMI with AQE - #29484 . Similarly for LEFT ANTI join without condition, we can convert join logical plan node to an empty relation if right build side is not empty. Will submit a followup PR tomorrow.
In addition, after taking a deep look at
BroadcastNestedLoopJoinExec(never looked closely to that because it's not popular in our environment), I found many places that we can optimize:outputOrderingandoutputPartitioningwhen possible to avoid shuffle/sort in later stage.LEFT SEMI/ANTIindefaultJoin()as we don't need to look through all rows when there's no join condition.I will file an umbrella JIRA with minor priority and do it gradually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see. That sounds reasonable. Nice idea, @c21 .