You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I'm facing a problem while attempting to query a Parquet file using OctoSQL. The Parquet file is sourced from the "TLC Trip Record Data" dataset (available here), containing NYC taxi trip records.
The error message I'm encountering is as follows:
Error: couldn't run query: couldn't run source: couldn't read row: decoding page 0 of column "VendorID": decoding definition levels of data page v1: RLE: decoded run-length block cannot have more than 1048576 values
It seems to be a decoding issue while trying to read the "VendorID" column from the Parquet file. It's worth noting that I have successfully read this file using other tools like dsq, and it's also accessible via online Parquet viewers like parquetreader.com and tablab.app.
Steps to Reproduce:
Install OctoSQL version 0.12.2.
Attempt to query the Parquet file using OctoSQL.
Expected Behavior:
OctoSQL should be able to successfully query the Parquet file without encountering decoding errors.
Actual Behavior:
OctoSQL encounters a decoding error related to the "VendorID" column, as mentioned above.
Description:
I'm facing a problem while attempting to query a Parquet file using OctoSQL. The Parquet file is sourced from the "TLC Trip Record Data" dataset (available here), containing NYC taxi trip records.
The error message I'm encountering is as follows:
It seems to be a decoding issue while trying to read the "VendorID" column from the Parquet file. It's worth noting that I have successfully read this file using other tools like
dsq
, and it's also accessible via online Parquet viewers like parquetreader.com and tablab.app.Steps to Reproduce:
Expected Behavior:
OctoSQL should be able to successfully query the Parquet file without encountering decoding errors.
Actual Behavior:
OctoSQL encounters a decoding error related to the "VendorID" column, as mentioned above.
Additional Information:
The text was updated successfully, but these errors were encountered: