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** Unable to create table off a directory without specifying the file format, even if all files have the same and a descriptive extension, such as `.parquet` ![60B8624A-1EF7-4543-BC03-8D9D76ABBE83](https://user-images.githubusercontent.com/5353722/112559604-52004d00-8d9f-11eb-98aa-a29bb312ad04.jpeg)

bug

GPUCI only tests the local filesystems. We want to improve our coverage. We want to be able to tests a subset of the e2e tests that can run on various...

We want to test various sizes but are still just assuming one and two nodes for execution for the time being. I think that we can test on 1GB and...

**Current state** The `do_process` function interface currently takes `std::shared_ptr output` as input and additionally a `task` also takes in `std::shared_ptr output` in the contructor. Originally, the idea was that a...

We need to start gaining an understand of how CBO works in the context of Calcite and how we can start leveraging it. We have done some research on this...

This is not a released version so we can't do this quite yet but at some point we need to update to the latest calcite or update to 1.26 and...

**Why we need window functions?** When working with big data window functions help to slice the things out like removing the duplicated with rank/row number/dense rank without theses inbuilt functions...

feature request

- [ ] Providers must be done - [ ] Use of provider and parser inside the kernels must be done - [ ] e2e for both must be done...

This Issue assumes that PR https://github.com/BlazingDB/blazingsql/pull/1426 has been merged. The design for this feature can be found here: https://docs.google.com/document/d/1DQMEps8Wgx757AS1GnDqGdeJiW88C7mLSLGOD_aaonQ/edit?usp=sharing

* Add generator into blazing/tests * Provide a way to automate the sql coverage script * Have a way to know when we are improving our SQL coverage (this may...