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
I was looking at the benchmark queries to get an idea of what more complex Weld queries look like, and I think I stumbled across a bug in the following part of the query:
Here values are grouped by returnflag * 2 + linestatus. However, as the value for returnflag ranges from 0 to 1 (inclusive), and that for linestatus from 0 to 2 (inclusive), this means that any value with (returnflag=0, linestatus=2) will be mapped to the same group values with (returnflag=1, linestatus=0), as both will be mapped to index 2 == (0*2+2) == (1*2+0).
Changing the mapping to i64(e.$0*3c + e.$1) should solve the issue.
The text was updated successfully, but these errors were encountered:
I was looking at the benchmark queries to get an idea of what more complex Weld queries look like, and I think I stumbled across a bug in the following part of the query:
Here values are grouped by
returnflag * 2 + linestatus
. However, as the value for returnflag ranges from 0 to 1 (inclusive), and that for linestatus from 0 to 2 (inclusive), this means that any value with (returnflag=0, linestatus=2) will be mapped to the same group values with (returnflag=1, linestatus=0), as both will be mapped to index2 == (0*2+2) == (1*2+0)
.Changing the mapping to
i64(e.$0*3c + e.$1)
should solve the issue.The text was updated successfully, but these errors were encountered: