Streaming secondary indices: incremental, demand-driven index evaluation

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 12 Jan, 00:00 UTC

ClickHouse now streams secondary index evaluation alongside data reads instead of scanning indexes upfront, making index usage incremental and demand-driven, reducing startup latency, unnecessary work, and memory usage.

Sources

• T1Streaming secondary indices: incremental, demand-driven index evaluationDatabricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale12 Jan, 00:00