Closed gumdropsteve closed 4 years ago
felipeblazing
commented
4 years ago We are currently looking into this issue. It seems to be an issue with the relational algebra that is being generated. Will update here with information about the PR for this
gumdropsteve
commented
4 years ago EDIT: just tried without messing with key and without feeding BlazingContext the column names, both had same result.
@felipeblazing I was able to run the query seen in this tweet in the same environment: https://twitter.com/blazingsql/status/1192163166580432897
Might be more to do with extracting values from datetime column key? Or maybe that the table in this query is originated in BlazingContext rather than cudf? Hope this is useful. Thanks.
felipeblazing
commented
4 years ago Seems to be an issue with calcite. We need to push a fix. Will assign someone tomorrow
On Wed, Nov 6, 2019, 7:23 PM Winston notifications@github.com wrote:
Update (Additional Info)
@felipeblazing https://github.com/felipeblazing I was able to run the query seen in this tweet in the same environment: https://twitter.com/blazingsql/status/1192163166580432897
[image: image] https://user-images.githubusercontent.com/43570913/68349329-ab37e580-00b1-11ea-8136-b2542362b70f.png Thoughts
Might be more to do with extracting values from datetime column key? Or maybe that the table in this query is originated in BlazingContext rather than cudf? Hope this is useful. Thanks.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/BlazingDB/pyBlazing/issues/120?email_source=notifications&email_token=AD7LELOHSVEQLWAHEPLSDUDQSNNZZA5CNFSM4JIJ7XB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDIOXOA#issuecomment-550562744, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD7LELIGPA74DFGOCCE63XLQSNNZZANCNFSM4JIJ7XBQ .
aucahuasi
commented
4 years ago Thanks @gumdropsteve! @rommelDB is working on this one!
rommelDB
commented
4 years ago Hey @gumdropsteve, thanks for the report. This PR https://github.com/BlazingDB/blazingdb-calcite/pull/41 fixes such an issue. It will be merged to develop soon! cc @aucahuasi
Describe the bug
Provided alias column names are not applying to columns of query results which are instead generically titled $f0, $f1 ... $fn.
Context After creating a table ("taxi"), I'm trying to:
but the new time column names (hours, months, years) are being output as $f0, $f1 and $f2, and the distance column names (longitude_distance, latitude_distance) are being output as $f3 and $f4.
Here's the query and execution:
Here's the current output:
Steps/Code to reproduce bug
Here's the notebook in Colab: https://colab.research.google.com/drive/1gEX0CrTMNLu5Y4V4JbLw5HAQm6UHgtAr
Dataframe with incorrect column names output is displayed and can be reproduced by downloading and running the notebook locally. Currently there is a manual correction fix in place.
Expected behavior
Environment overview
Environment details