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
[SPARK-32708] Query optimization fails to reuse exchange with DataSourceV2 #29564
Closed
Closed
Changes from 5 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
d46483f
[SPARK-32609] Incorrect exchange reuse with DataSourceV2
mingjialiu 5b1b9b3
[SPARK-32609] Incorrect exchange reuse with DataSourceV2
mingjialiu dd0fb24
[Spark 32708] Query optimization fails to reuse exchange with DataSou…
mingjialiu 4ba92cc
Merge branch 'branch-2.4' of https://github.com/mingjialiu/spark into…
mingjialiu 704efbc
Merge remote-tracking branch 'upstream/branch-2.4' into branch-2.4
mingjialiu 69ea44e
[SPARK-32708] Query optimization fails to reuse exchange with DataSou…
mingjialiu 2fe41e0
Merge branch 'branch-2.4' of https://github.com/mingjialiu/spark into…
mingjialiu a6e4709
Revert "[Spark 32708] Query optimization fails to reuse exchange with…
mingjialiu 98483c8
[SPARK-32708] Query optimization fails to reuse exchange with DataSou…
mingjialiu 8b864e7
[SPARK-32708] Query optimization fails to reuse exchange with DataSou…
mingjialiu acadafe
Merge remote-tracking branch 'upstream/branch-2.4' into branch-2.4
mingjialiu File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
Why we need to change Expression to Filter, which is a public interface?
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.
More explanation. Why changing from Expression to org.apache.spark.sql.sources.Filter
DataSourceV2ScanExec.pushedFilters are defined as array of Expressions whose equal function has expression_id in scope. So for example, Expression isnotnull(d_day_name#22364) is not considered equal to isnotnull(d_day_name#22420). Therefore, the right thing is to define and compare pushedFilter as Filter class.
At both Spark 3.0 and affected Spark 2.4's tests suite, Filter is the class being used. And the above 4 places seem to be the only places that miss to have pushedFilter as class Filter.
(Because pushedFilters are defined the right way in the above test suite, Spark 32708 was not caught by my tests previously added for SPARK-32609, another exchange reuse bug.
Usage of Expression was introduced by PR [SPARK-23203][SQL] DataSourceV2: Use immutable logical plan. From the PR's description and original intention, I don't see a necessary reason to maintain Expression.