search

luusluus / vscode-parquet-visualizer

vscode extension for SQL querying and visualizing parquet files
https://marketplace.visualstudio.com/items?itemName=lucien-martijn.parquet-visualizer
MIT License
3 stars 0 forks source link

SQL stopped executing properly as of 0.11.0 #69

Open darrylthom opened 4 hours ago

darrylthom commented 4 hours ago

Prior to 0.11.0, I could run SQL on my 600 kb Parquet file successfully. Now it hangs on "Loading..." for every query executed.

Opening the file is successful and so is viewing all of the tabs within Visual Studio. It's specifically when I run SQL.

luusluus commented 4 hours ago

Sorry to hear this happened. Are you willing to share the parquet file for debugging?

darrylthom commented 4 hours ago

Sample.zip

luusluus commented 4 hours ago

Thank you I'll take a look asap.

luusluus commented 4 hours ago

I have parquet-visualizer version 0.13.1 installed on my vscode desktop installation and the querying works fine for me.

OS: Linux Arch: x64 UI: desktop vscode version: 1.95.3

I'll try to install 0.11.0 and retry

luusluus commented 3 hours ago

Trying 0.11.0 and the query 

SELECT *
FROM data
LIMIT 1000;

works fine as well.

darrylthom commented 3 hours ago

My setup:

Windows 10 Enterprise 64 bit VS: 1.95.3

luusluus commented 3 hours ago

Can you try upgrading to the latest version?

luusluus commented 3 hours ago

I'll try to do it in a windows environment as well

darrylthom commented 3 hours ago

Stuck on Loading for me in 0.13.1

luusluus commented 3 hours ago

Yes! I reproduced the error. I'll come with a fix ASAP.

Thanks for reporting.

luusluus commented 3 hours ago

In the meanwhile, you could try Windows Subsystem For Linux (WSL) on your windows machine and open vscode in a linux environment to continue your work.

darrylthom commented 3 hours ago

Thanks! Would it also be possible with the Exporting option, to make a setting where it can prompt you where you want the file to output?

Maybe it could default to the last location you manually saved it. Right now, it is a bit unfavorable that it outputs the exports in the same folder as the parquet since we stage ours on a network share meant for production data.

A to Excel (.xlsx) option would also be amazing, but probably asking for too much.