Re:A sharded DuckDB on 63 nodes runs 1T row aggregation chal...
by lopatin on Friday October 24, 2025 @01:08PM
(#45696700)
DuckDB is great but it’s barely OLAP right? A key part of OLAP is “online”. Since the writer process blocks any other processes from doing reads, calling it OLAP is a stretch I think.
[ Parent
| on HN ]
Re:A sharded DuckDB on 63 nodes runs 1T row aggregation chal...
by ansgri on Friday October 24, 2025 @02:17PM
(#45697514)
Isn't the Online part here about getting results immediately after query, as opposed to overnight batch reports? So if you don't completely overwhelm DuckDB with writes, it still qualifies. The quality you're describing is something like "realtime analytics", and is a whole another category: Clickhouse doesn't qualify (batching updates, merging etc. — but it's clearly OLAP), Druid does.
Re:A sharded DuckDB on 63 nodes runs 1T row aggregation chal...
by lopatin on Friday October 24, 2025 @02:47PM
(#45697833)
Huh yeah looks like I was totally wrong about what online meant. So yeah DuckDB is OLAP. Not that anyone was asking me in the first place. Carry on :)
Re:A sharded DuckDB on 63 nodes runs 1T row aggregation chal...
by sdairs on Friday October 24, 2025 @02:49PM
(#45697848)
ClickHouse is the market leader in real-time analytics so it's an interesting take that you don't think it qualifies.
Re:A sharded DuckDB on 63 nodes runs 1T row aggregation chal...
by ansgri on Friday October 24, 2025 @05:42PM
(#45699399)
For certain definition of realtime, certainly (as would any system with bounded ingestion latency), but it’s not low-latency streaming realtime. Tens of seconds or more can pass before new data becomes visible in queries in normal operation. There’s batching, there’s merging, and its overall architecture prioritizes throughput over latency.