-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[SPARK-35855][SQL] Unify reuse map data structures in non-AQE and AQE rules #33021
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
peter-toth
wants to merge
2
commits into
apache:master
from
peter-toth:SPARK-35855-unify-reuse-map-data-structures
Closed
Changes from all commits
Commits
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
73 changes: 0 additions & 73 deletions
73
sql/catalyst/src/main/scala/org/apache/spark/sql/util/ReuseMap.scala
This file was deleted.
Oops, something went wrong.
73 changes: 0 additions & 73 deletions
73
sql/catalyst/src/test/scala/org/apache/spark/sql/util/ReuseMapSuite.scala
This file was deleted.
Oops, something went wrong.
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
These slight changes are needed to avoid
ReuseExchange
nodes in the test plans and keep the original test logic as this PR changes theReuseExchangeAndSubquery
rule to identify reuses based on canonicalized plans only (the schema of the exchanges are no longer need to match).Without these changes the canonicalized plans of
LocalTableScanExec
in t1, t2 and t4 are the same as they have the same content.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.
@peter-toth are you saying that the new logic may reuse an exchange even if the schema doesn't match? The canonicalized form of the plan doesn't consider schema?
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.
Schema contains the name of the output attributes as well, but in canonicalized plans we always replace names to "none" and only the structure of plan matters.
Please also note that
ReusedExchangeExec
captures the output of the original exchange so that can we restore the schema in aReusedExchangeExec
.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 see, so the new logic is more effective (can trigger reuse in more cases), and we need to update the test here to not trigger reuse.
Uh oh!
There was an error while loading. Please reload this page.
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.
Yes it is, but I don't think this comes up frequently in real world applications.
Changing
t2
andt4
seemed easier than preparing the test for reused exchanged.I also looked into why the issue didn't come up with the AQE version of the suite (
BroadcastJoinSuiteAE
) before this PR and that's because the test doesn't run the queries before inspecting the plans and the initial AQE plans don't contain reuses (but final plans do).