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
Trying out your reproducer with latest main gives me an error 😕 looks like at some point between now and 2023.6.0 our logical plan has changed such that we skip the casting of the non-string column:
# 2023.6.0
Projection: Utf8("A") || CAST(t1.c0 AS Utf8)
TableScan: t1 projection=[c0]
# main
Projection: Utf8("A") || t1.c0
TableScan: t1 projection=[c0]
Leading to errors in the binary operation; cc @jdye64 if you have any capacity to look into this. As for the original issue, it seems like that generally comes down to difference in the behavior of cast operations on CPU/GPU, as the following shows the same issue:
print('CPU Result:')
result1=c.sql("SELECT CAST(c0 AS STRING) FROM t1").compute()
print(result1)
print('GPU Result:')
result2=c.sql("SELECT CAST(c0 AS STRING) FROM t1_gpu").compute()
print(result2)
Can look into that, would you mind modifying your issue description / title to reflect this?
Thanks for your confirmation.
We look forward to your replies about bug fixes.
qwebug
changed the title
[BUG][Logic Bug] "SELECT (<string>)||(<column(decimal)>) FROM <table>" brings Error
[BUG][GPU Logic Bug] "SELECT (<string>)||(<column(decimal)>) FROM <table>" brings Error
Jan 22, 2024
This problem came up at dask-sql version: 2023.6.0 .
And it has been fixed at dask-sql version: 2024.3.0, after my verification.
Thanks to the developers for their contributions.
What happened:
"SELECT (<string>)||(<column(decimal)>) FROM <table>" brings different results, when using CPU and GPU.
What you expected to happen:
It is the same result, when using CPU and GPU.
Minimal Complete Verifiable Example:
Result:
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: