If you query a Parquet file from your lake via DuckDB-in-browser, does DuckDB run in WASM on the web client and pull the compressed parquet to your browser where it is decompressed?
Or are you connecting some DuckDB on the web client to some DuckDB component on a server somewhere?
I presume yes to the first and no to the second but just checking I have my mental model correct.
If you query a Parquet file from your lake via DuckDB-in-browser, does DuckDB run in WASM on the web client and pull the compressed parquet to your browser where it is decompressed? Or are you connecting some DuckDB on the web client to some DuckDB component on a server somewhere?
I presume yes to the first and no to the second but just checking I have my mental model correct.