3 ms·
And now I'm curious whether there's a way to actually index external files (make these queries over 600GB faster) and have this index (or many indices) be persi
by touisteur 1y ago
And now I'm curious whether there's a way to actually index external files (make these queries over 600GB faster) and have this index (or many indices) be persistent. I might have missed that when I looked at the docs...
- wenc 1y agoIf the data is in Parquet they are already indexed in a sense. No further indexing necessary. If they are stored in DuckDB’s native format (which I don’t use), it supports some state of the art indices. https://duckdb.org/docs/stable/sql/indexes.html https://duckdb.org/docs/stable/sql/indexes.html I find Parquet plenty fast though.
- touisteur 1y agoAh thanks, of course. I was thinking of dealing with millions of (Geo)JSON files adding up to terabytes, without copying/duplicating them though, mostly indexing. I used to do that with postgres foreign data wrappers and had hopes for duckdb :-). But that's a question for SO or other forum.