-
Notifications
You must be signed in to change notification settings - Fork 599
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
Revisit Impala's CASE expression type precedence rules #93
Comments
The postgres algorithm for deciding the output type looks reasonable here: https://www.postgresql.org/docs/current/static/typeconv-union-case.html |
@cpcloud This issue seems a bit outdated, should we still revisit? |
This is really a backlog issue, that we may or may not get to after other higher priority issues are done. We can still leave it open though. |
Hi all, I am trying the follow code but it raises an error: t0 = ibis.table(
[('one', 'string'),
('two', 'double'),
('three', 'int32')], 'my_data')
expr = (
t0.three
.case()
.when(0, 'low')
.when(1, 'high')
.else_('null')
.end()
.name('label')
)
print(t0[expr].limit(10).compile()) How can I allow this? I need it because I am creating a backend and it allow this kind of operation. |
@xmnlab This looks like a bug since the types you've written in your example are perfectly valid. |
I'm going to move your example to a separate issue. |
Closing as stale. |
Issue by wesm
Friday Jan 30, 2015 at 22:37 GMT
Originally opened as http://github.mtv.cloudera.com/wesm/ibis/issues/93
see #31
The text was updated successfully, but these errors were encountered: