-
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
Incorrect CASE WHEN + ELSE NULL behavior #13885
Labels
bug
Something isn't working
Comments
this happens in |
possibly related: #13779 |
richox
pushed a commit
to kwai/blaze
that referenced
this issue
Dec 24, 2024
fix parsing parquet int96 to timestamp error. fix compatibility of casting str to int. fix Incorrect CASE WHEN + ELSE NULL behavior (apache/datafusion#13885). use number of physical cores as tokio parallelism, removing blaze.tokio.num.worker.threads. sort multiple batches with interleaver in repartitioner. use in-place radix sort. use sync channel in ipc reading.
Merged
gy11233
pushed a commit
to kwai/blaze
that referenced
this issue
Dec 24, 2024
fix parsing parquet int96 to timestamp error. fix compatibility of casting str to int. fix Incorrect CASE WHEN + ELSE NULL behavior (apache/datafusion#13885). use number of physical cores as tokio parallelism, removing blaze.tokio.num.worker.threads. sort multiple batches with interleaver in repartitioner. use in-place radix sort. use sync channel in ipc reading. Co-authored-by: zhangli20 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
some queries containing
case when .. ELSE NULL end
produces incorrect results.To Reproduce
preparing test table:
query:
Expected behavior
the above query should always output nulls, since the only WHEN condition is always null (not true)
Additional context
No response
The text was updated successfully, but these errors were encountered: