chDB for Node 3.6.0 and Rust 2.2 are out, on stable chdb-core 26.11.1.
Both add direct Arrow: register an Arrow table or batch reader as a SQL source, stream typed RecordBatches back, no IPC serialization.
cargo add chdb-rust
github.com/chdb-io/chdb-node…
github.com/chdb-io/chdb-rust…
63
chDB chdb-core v26.11.1 is out, on ClickHouse 26.11.
Polars in and out: query a DataFrame, LazyFrame or Series in place, get a Polars DataFrame back.
pip install -U chdb-core
chdb.query("SELECT sum(a) FROM Python(lf)", "polars")
github.com/chdb-io/chdb-core…
Your next on-call incident is a dating sim.
High Cardinality lets you date Logs, Metrics and Traces, with chDB running ClickHouse in your browser.
One of them only shows up to 1% of your dates. Naturally.
highcard.love/
74
Parquet integrity test: flip one byte inside a checksummed data page, then sum the column. In a June run, chDB 4.1.8 raised "Page CRC checksum verification failed" by default. pyarrow ships the check but leaves it off, so it returned a wrong sum. github.com/flying-coyote/sdw…
2
130
CI lesson from Cerberus by @tsouza: chDB already spreads one query across cores, so more test processes per runner backfired (8 on an 8-core box ran slower than 4). Their 900+ PromQL roundtrip fixtures now run ~3 processes per runner over 6 runners.
github.com/tsouza/cerberus/b…
1
104
Someone built a dating sim where you date Logs, Metrics and Traces.
Traces only shows up to 1% of your dates 😂
It runs real ClickHouse in your browser via chDB WASM. You can turn on SQL to see the checks behind the story.
I had to check. It works.
highcard.love/
Everr's local mode runs a fork of the upstream OTel ClickHouse exporter on embedded chDB. @everrlabs swapped the network connection for an in-process chDB handle and turned batch inserts into JSONEachRow, so laptop and cloud share one schema.
github.com/everr-labs/everr/…
chDB retweeted
If a distributed #ClickHouse® query is slow, total runtime only tells you so much. What was each node actually doing? 🤔
We traced a GROUP BY across 2 shards/2 replicas to see which nodes handle the query & how partial aggregates get merged in this demo: hubs.la/Q04DS01W0
記事を投稿しました! ClickHouse 26.10 で等号の無い JOIN を範囲の突き合わせで試してみた [SQL] on #Qiita qiita.com/asahide/items/b458…
vault-recall by @Tony_Stef_ turns a folder of markdown notes into an MCP memory for coding agents. Its optional chDB backend keeps vectors in a MergeTree table with exact cosineDistance; the same SQL runs on a ClickHouse server.
github.com/tonydzi/vault-rec…
2
159
Nix users can now pin chDB like any other dependency: engram packages libchdb, the Python module and a chdb-rust example, hash-pinned and checked on nixpkgs unstable, 26.05 and 25.11 (x86_64-linux for now).
github.com/levigross/engram
71
Give your data agent a cheap "did anything change?" tool before it diffs rows:
SELECT _file, count() n, sum(cityHash64(*)) h
FROM file('exports/*.parquet')
GROUP BY _file
Order-independent, no ETL. On 10M rows in chDB: 0.22s, 0.4 GB. A full two-way EXCEPT took 3.2s and ~4 GB.
1
111
chDB retweeted
Every coding-agent session shouldn’t have to start from zero.
Loom is an open-source agent memory system built on ClickHouse. It keeps what agents learn connected to a live code index, so the next session starts with context that still matches the code.
Meet Loom: clickhouse.com/blog/introduc…
【PyCon JP 2026】Rediscovering DataFrames 100× Analytics Without Leaving P... youtu.be/ndmIZxi8A-M?si=12Ze… via @YouTube
chDB retweeted
Replying to @auxten
Xata's copy-on-write Postgres branches next to ClickHouse feels like a natural pairing: spin up a branch of prod for a preview env and point analytics at it without touching the primary. Curious whether that branching ends up in ClickHouse's managed Postgres.
Replying to @monicasarbu
It is exciting to imagine: Xata, our managed PostgreSQL team, and pg_chdb coming together to create a product with such incredible technical vision!










