News for hackers. Stuff that matters.

A comment on DuckDB-Wasm: Efficient analytical SQL in the browser. Parent comment

Re:DuckDB-Wasm: Efficient analytical SQL in the browser by ankoh on Friday October 29, 2021 @12:04PM (#29040120)
Yes we do! DuckDB-Wasm can read files using HTTP range requests very similar to the sql.js-httpvfs from phiresky.

The blog post contains a few examples how this can be used, for example, to partially query Parquet files over the network.

E.g. just visit shell.duckdb.org and enter:

select * from 'https://shell.duckdb.org/data/tpch/0_01/parquet/orders.parqu...' limit 10;

[ Parent | on HN ]
Re:DuckDB-Wasm: Efficient analytical SQL in the browser by 1egg0myegg0 on Friday October 29, 2021 @12:07PM (#29040164)
NIIIICE! Data twitter was pretty excited about that cool SQLite trick - now you can turn it up a notch!
[ Parent | on HN ]
Re:DuckDB-Wasm: Efficient analytical SQL in the browser by tomrod on Friday October 29, 2021 @02:31PM (#29041974)
Is data twitter == #datatwitter, like Econ Twitter is #econtwitter?

If so, I have another cool community to follow!

[ Parent | on HN ]
Re:DuckDB-Wasm: Efficient analytical SQL in the browser by obeliskora on Friday October 29, 2021 @01:32PM (#29041249)
It would be really cool to load duckdb files too. sql.js-httpvfs seems convenient because it works on everything in database so you don't have to create indexes, or setup keys and constraints in the client.
[ Parent | on HN ]
Re:DuckDB-Wasm: Efficient analytical SQL in the browser by ankoh on Friday October 29, 2021 @02:45PM (#29042147)
I agree! DuckDB-Wasm can already open DuckDB database files in the browser the very same way.
[ Parent | on HN ]
Re:DuckDB-Wasm: Efficient analytical SQL in the browser by obeliskora on Friday October 29, 2021 @12:19PM (#29040318)
That's really neat! Can you control the cache too?
[ Parent | on HN ]
Re:DuckDB-Wasm: Efficient analytical SQL in the browser by ankoh on Friday October 29, 2021 @12:23PM (#29040360)
DuckDB-Wasm uses a traditional buffer manager and evicts pages using a combination of FIFO + LRU (to distinguish sequential scans from hot pages like the Parquet metadata).
[ Parent | on HN ]