feat: Optimize CASE expression for usage where then and else values are literals #11553
Conversation
github-actions
bot
added
physical-expr
andygrove
changed the title
| .unwrap_or_else(|_| Arc::clone(e)); | ||
| let else_ = Scalar::new(expr.evaluate(batch)?.into_array(1)?); | ||
|
|
||
| Ok(ColumnarValue::Array(zip(&when_value, &then_value, &else_)?)) |
There was a problem hiding this comment.
if the input is ColumnarValue::Scalar shouldn't the output also be a ColumnarValue::Scalar (rather than a ColumnarValue::Array?)
There was a problem hiding this comment.
No, the output will be an array containing values based on two scalar arguments.
SELECT CASE WHEN a > 2 THEN 'even' ELSE 'odd' END FROM foo
----
odd
even
even
There was a problem hiding this comment.
I wonder if it would make sense (in a separate PR) to produce a dictionary array in this case since it will only even contain two distinct values? 🤔
| 4 | ||
| 6 | ||
|
|
||
| # scalar or scalar (string) |
There was a problem hiding this comment.
Could you also add a test where both arguments are scalars (like CASE WHEN 1 > 2 THEN 'true' ELSE 'false') ?
|
|
||
| # scalar or scalar (string) | ||
| query T | ||
| SELECT CASE WHEN a > 2 THEN 'even' ELSE 'odd' END FROM foo |
There was a problem hiding this comment.
Looks like NULL handling in this specialized implementation is not tested, we can add a (NULL, NULL) row into foo table
There was a problem hiding this comment.
Good point. I have added this.
…re literals (apache#11553) * Optimize CASE expression for usage where then and else values are literals * add slt test * add more test cases
4 participants
Which issue does this PR close?
N/A
Rationale for this change
What changes are included in this PR?
Add a fast path for a specific usage of CASE expression
Are these changes tested?
Are there any user-facing changes?