-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Move sql_compound_identifier_to_expr
to ExprPlanner
#11487
Merged
Merged
Changes from 12 commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
ba92a84
move get_field to expr planner
dharanad 44118b9
formatting
dharanad 404347e
formatting
dharanad 1adc9a4
documentation
dharanad 5f4ac70
refactor
dharanad 38debfc
documentation & fix's
dharanad 6623219
move optimizer tests to core
dharanad 040dc3c
Merge branch 'refs/heads/main' into move-get-field-expr-planner
dharanad 73cf5fa
fix breaking tc's
dharanad e4a7d7c
cleanup
dharanad 7c52b3d
fix examples
dharanad 2ab18e4
formatting
dharanad 9378d15
rm datafusion-functions from optimizer
dharanad 1379cd7
update compound identifier
dharanad d6c3590
update planner
dharanad d2fa19a
update planner
dharanad 3076d54
formatting
dharanad 091260f
Merge branch 'refs/heads/main' into move-get-field-expr-planner
dharanad 40ab63c
reverting optimizer tests
dharanad 671ee93
formatting
dharanad 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
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 are these tests moved? Does that mean we can't plan SQL with identifiers like
test.col_int32
without an Expr planner?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.
For the earlier implementation, I also moved plannig of basic SQL like column references to expr planner, we had to move these test cases from
optimizer
crate tocore
to avoidoptimizer
crate dependecy onfunctions
.Since we have moved that out of planner, ideally i should moved the testcases back. My bad, i missed them. Thanks for catching this. I have fixed this.