-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-50245][SQL][TESTS] Extended CollationSuite and added tests where SortMergeJoin is forced #48774
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
vladanvasi-db
wants to merge
4
commits into
apache:master
from
vladanvasi-db:vladanvasi-db/collation-suite-test-extension
Closed
[SPARK-50245][SQL][TESTS] Extended CollationSuite and added tests where SortMergeJoin is forced #48774
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
81b08fc
Extended CollationSuite and added tests where SortMergeJoin is forced
vladanvasi-db 265efcd
Refactored test suite to reduce code
vladanvasi-db 9851790
Simplified assertions for SortMerge and HashJoin
vladanvasi-db ba3e702
Moved collation key check into common helper function
vladanvasi-db 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
Next
Next commit
Extended CollationSuite and added tests where SortMergeJoin is forced
- Loading branch information
commit 81b08fc99408819034edfe4af2c40f5903adafcd
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
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.
would it maybe be easier to run the tests with default and -1 values of the conf, and then just assert that different joins are used based on the conf's value?
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.
feels like we would avoid a lot of code duplication with this approach
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.
how about smth like this
i.e. iterating over possible vals, to reduce duplication
can also conditionally collect join plan nodes, based on val
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.
Did exactly this, the asserts for
SparkPlannodes are refactored, however, thecollationKeycheck in the plan could not be refactored like the asserts, so there are some duplications in the code, but not significant.