-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
unwrap_cast_in_comparison
: fix bug which can find the field for the schema
#3699
Conversation
We can close this pr: #3694 cc @andygrove @alamb I migrate some test in #3694 to this pr, thanks @andygrove |
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 think the test coverage is good -- there are some additional improvements I think we could do, but maybe in a follow on PR
fn case_when() -> Result<()> { | ||
let sql = "SELECT CASE WHEN col_int32 > 0 THEN 1 ELSE 0 END FROM test"; | ||
let plan = test_sql(sql)?; | ||
let expected = "Projection: CASE WHEN #test.col_int32 > Int32(0) THEN Int64(1) ELSE Int64(0) END\ |
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.
This plan doesn't look ideal to me -- since col_int32
is int32 I think the exprs could be rewritten to
CASE WHEN #test.col_int32 > Int32(0) THEN Int32(1) ELSE Int32(0) END
Could be done as a follow on PR for sure
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.
@alamb yes,
we can support the unsigned numeric data type in the UnwrapCastInBinaryComparison
rule
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.
Benchmark runs are scheduled for baseline = d0760f3 and contender = 5731228. 5731228 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
Closes #3690
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?