dask-sql

dask-sql copied to clipboard

**What happened**: "SELECT ((\) IS DISTINCT FROM ((CASE \ WHEN \ THEN \ END ))) FROM \" brings different results, when using CPU and GPU. **What you expected to happen**:...

qwebug

[BUG]] [GPU Logic Bug] "SELECT ((1) NOT BETWEEN (CASE ((<column>)) WHEN (1) THEN 0 END ) AND (<column>)) FROM <table>" brings Error

1

**What happened**: "SELECT ((1) NOT BETWEEN (CASE ((\)) WHEN (1) THEN 0 END ) AND (\)) FROM \" brings different results, when using CPU and GPU. **What you expected to...

qwebug

[BUG][GPU Logic Bug] "SELECT (<string>)||(<column(decimal)>) FROM <table>" brings Error

4

**What happened**: "SELECT (\)||(\) FROM \" brings different results, when using CPU and GPU. **What you expected to happen**: It is the same result, when using CPU and GPU. **Minimal...

qwebug

Pin as many deps as possible in 3.9 GPU CI environment

1

This should make this environment consistent with that used in GPU CI as of https://github.com/rapidsai/dask-build-environment/pull/83

charlesbluca

Bump datafusion-python to 34.0.0

1

charlesbluca

[BUG][GPU Error Bug] "SELECT ((<string>)!=(<column>)) FROM <tables>" brings Error

5

**What happened**: "SELECT ((\)!=(\)) FROM \" brings error, when using GPU. However it is able to output result, when using CPU. **What you expected to happen**: It will not bring...

qwebug

Attempt to enable local dynamic TLS for aarch64 builds

1

charlesbluca

More restrictive input validation during predicate pushdown filter extraction

1

While running some TPC-H queries using dask-sql + dask-cudf, I noticed some failures around predicate pushdown that seemed to be caused by us incorrectly pushing down blockwise comparisons between columns....

charlesbluca

Riight now, many trivial SQL queries are failing due to Dask dataframe config defaults not being supported in Dask-SQL right now: ```python from dask_sql import Context from tests.integration.test_compatibility import make_rand_df...

charlesbluca

Use aliased column names for cross joins

1

Because we were forgetting to alias/unalias column names before/after the merge operation, tables sharing column names were not being handled properly

charlesbluca