William Malpica
William Malpica
@felipeblazing what is this feature? why does it change so many files? I am assuming it was based off of some other branch. Which PR needs to be merged before...
@argenisleon thank you for filing this issue. This is a feature we do want to enable. The main issue here is at the query parsing and how that is handled...
@lucharo BSQL currently does not support DECIMAL. Its on our roadmap. Until we do, can address this issue for expanding that `cudfTypeToCsvType` mapping to include DECIMAL, and we would have...
Right now the latest version you can get for Visual Studio Code, which is what a lot of us use is: clang-format version 11.1.0 So perhaps we shoot for that...
This looks great, but as @Christian8491 mentiones, we will need new data types internally to really roll this out. So this PR is for now, just a placeholder for future...
PR #1387 helps address this issue by skipping metadata collection for some types of columns. But this issue should still be revisited by actually implementing proper metadata collection for these...
Basic info about BlazingSQL architecture: https://docs.google.com/document/d/1VJghfZLWleojxYZBRo6v3CZwzdnfHaLtMJm462TVeOA/edit?usp=sharing Starting info about how to start implementing Window functions: https://docs.google.com/document/d/1EF0198yxlt3Uu6jJ6Yw_MkQls8gGWDolifjZhBbLXDg/edit?usp=sharing
We should make sure we look at this https://github.com/BlazingDB/blazingsql/pull/878 when implementing this feature
Other associated issues: #1478 #1450
Here is my design proposal for this: 1. The current user facing API for BlazingContext and bc.sql stay the same. A dictionary called config_options. 2. Lets take the work that...