blazingsql icon indicating copy to clipboard operation
blazingsql copied to clipboard

BlazingSQL is a lightweight, GPU accelerated, SQL engine for Python. Built on RAPIDS cuDF.

Results 103 blazingsql issues
Sort by recently updated
recently updated
newest added

**Describe the bug** When my HDFS Kerbersised BlazingSQL `Connection` object is created it generates a lot of warnings and errors but the connection actually works, how can I remove the...

bug
? - Needs Triage

Dear all, Thank you for your great work on SQL query using GPU, it seems to be awesome ! As a beginner, I've tried to use BlazingSQL for querying data...

question

When running pipelines on geodata often you want to transform the data into h3 hexagons to then unify across datasets. **Describe the solution you'd like** Similar to these integrations you...

? - Needs Triage

Just submitting this PR to update `branch-21.10` of BlazingSQL with changes RAPIDS made to ensure compatibility with `cudf` `21.10`. This also contains `branch-21.08` commits that have not been forward merged....

When I process this sql: ``` SELECT 4 TIME_ID ,STOCK_ID ,MAX(CASE WHEN TIME_ID BETWEEN 4 - 1597 + 1 AND 4 - 1 + 1 THEN VAR12 ELSE null END)...

bug
? - Needs Triage

Hi, I'm using blazingsql in thread to execute about 20 select queries at the same time. I run this job and discovered that it takes much storage, about many hundreds...

bug
? - Needs Triage

``` PackagesNotFoundError: The following packages are not available from current channels: - rapids-blazing=21.08 ``` Been this way for last week.

bug
? - Needs Triage

**Describe the bug** This test was commented out because lately crashes randomly (from hiveFileTest.py file) This is the query in question. query = "select o_totalprice from orders where o_orderstatus =...

bug
? - Needs Triage

I am running into a following issue reading partitioned data from local disk. it reads am empty data frame. it is able to resolve the file paths very fine. but...

bug

**Describe the bug** Despite setting `bc(enable_logs=False, LOGGING_LEVEL='warn', ...)`, we are seeing debug logs being emitted to `algebra.log` and `blazing_log/pyblazing.log`. In a separate setup (dask-cuda workers), we're seeing `blazing_log/{RAL.0.log,pyblazing.0.log}`. This is...

bug