You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
AND/OR on the CPU in Spark will process the LHS unconditionally. But they will only process the RHS if they cannot figure out the result from just the lhs.
On the GPU we process both unconditionally, but in ANSI mode we can run into problems just like with #3849. We should do a similar fix for AND/OR like we did for IF/ELSE, and follow what Spark does on the CPU. For AND if the RHS has side effects we only process it for rows where the LHS is not false (this includes nulls). For OR if the RHS has side effects we only process it for rows where the LHS is not true (this includes nulls).
The text was updated successfully, but these errors were encountered:
Describe the bug
AND/OR on the CPU in Spark will process the LHS unconditionally. But they will only process the RHS if they cannot figure out the result from just the lhs.
On the GPU we process both unconditionally, but in ANSI mode we can run into problems just like with #3849. We should do a similar fix for AND/OR like we did for IF/ELSE, and follow what Spark does on the CPU. For AND if the RHS has side effects we only process it for rows where the LHS is not false (this includes nulls). For OR if the RHS has side effects we only process it for rows where the LHS is not true (this includes nulls).
The text was updated successfully, but these errors were encountered: