Full fireside chat: youtube.com/watch?v=_8DUJK8x…

Guillermo Rauch (@rauchg) explains how Vercel thinks about ClickHouse as part of its data infrastructure, and why agent-era applications need fast, direct access to data. Full fireside with Aaron Katz (@ceo_clickhouse), Guillermo Rauch, Tristan Handy (@jthandy), and Lukas Biewald (@l2k) in the comments. ⬇️

As always, we finish with recommending some reading materials!

Also, if you would rather we run ClickHouse for you instead of running it on your own....there are a number of new amazing features on ClickHouse Cloud.

We are officially out of time? But how do you ignore the integrations!

Related, do you love using PromQL? Maybe you can just use ClickHouse as Prometheus? ;)

What else is new in our support for @ApacheIceberg Parquet VARIANT support, and a new implementation of the unity catalog type. But that's not all, ClickHouse now applies deletion vectors when reading.

We continue with some features for data lakes. As a 'native' option, you can use the type: s3_plain_rewritable

Integration with Elasticsearch as a table engine and a table function? You can read documents from an index as a JSON column. Read-only...for now.

We aren't stopping there. A new query language for logs! LogsQL (the log query language of VictoriaLogs)

Alexey is now live-demoing usage of XGBoost dictionaries (train a gradient-boosted model at dictionary load)

We are adding a new cache type in ClickHouse!

Pushing the boundaries requires building experimental features. This talk is about to get very good.

SQLite was already supported as a database engine, the ability to attach a table, and use a table function. This has existed for 5 years. In 26.10 you can now use SQLite as a data format as well.

Are you aware that ClickHouse supports recursive CTE? We also have Materalized CTE. Now you can nest them. Super useful for graph traversal and tree structure traversal.

Query cache can now keep its entries in a filesystem cache!

And now onto "something interesting" (as if everything before wasn't already)

Even more improvements for @ApacheParquet !

This is one of Alexey's favourite optimizations. So I'm not going to try and give commentary...You should watch it live.

A similar optimization now exists for @ApacheParquet and @ApacheIceberg (also hdfs ;) )