-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat: Implement SessionState::create_logical_expr_from_sql_expr
#18423
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
Conversation
c718319 to
20f53ab
Compare
rkrishn7
left a comment
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.
Thanks @petern48! Looks good to me, although will need someone who can merge to sign off
| let query = SqlToRel::new_with_options(&provider, state.get_parser_options()); | ||
|
|
||
| for sql in ["[1,2,3]", "a > 10", "SUM(a)"] { | ||
| let sql_expr = state.sql_to_expr(sql, &dialect).unwrap(); |
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.
The api name is strange to me first, I think it wants to say "sql string to expr"
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.
Yeah, it can be a bit ambiguous. Either way, sql_to_expr is an existing public API before this PR.
|
Thanks @petern48 and @xudong963 |
…ache#18423) ## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes apache#123` indicates that this PR will close issue apache#123. --> - Closes apache#18278 ## Rationale for this change <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> Convenience method for when parsing has already been done, and we want to start from a an expr object instead of SQL string. ## What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> Added test ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> Yes, new public api. <!-- If there are any breaking changes to public APIs, please add the `api change` label. -->
Which issue does this PR close?
SessionState::create_logical_expr_from_sql_expr#18278Rationale for this change
Convenience method for when parsing has already been done, and we want to start from a an expr object instead of SQL string.
What changes are included in this PR?
Are these changes tested?
Added test
Are there any user-facing changes?
Yes, new public api.