ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #clickhouse
Learn how to diagnose and fix the 'Too many parts' error in ClickHouse by analyzing MergeTree part distribution and optimizing ingestion patterns.
Learn how to use ClickHouse Materialized Views and SummingMergeTree to shift telemetry aggregation from read-time to write-time, drastically reducing query latency for high-volume data.
Learn how ClickHouse materialized views can turn raw event tables into fast‑aggregated summaries, reducing dashboard latency while keeping data fresh.
Learn how to use ClickHouse’s Time‑to‑Live (TTL) feature to automatically expire data, with syntax, partitioning tips, a concrete example, monitoring guidance, and trade‑off analysis. Perfect for engineers building long‑term data pipelines.
Learn how to create, schedule, and monitor ClickHouse materialized views with refresh policies, ensuring up‑to‑date aggregates for dashboards while avoiding common pitfalls.
Learn how ClickHouse’s Distributed table engine can eliminate read bottlenecks in reporting dashboards. Step‑by‑step setup, a real query example, trade‑offs, and practical next steps to scale your cluster without rewriting code.
Goal Upgrade a small Java application’s ClickHouse schema without service interruption. The application uses the official JDBC driver and a ReplicatedMergeTree table that must stay writable during the change. Constraints ALTER TABLE ADD COLUMN with a default value temporarily locks writes on the shard. Drop‑and‑swap requires a brief window where the old tabl
ClickHouse manages server-side connection limits through the max_connections setting, while the HTTP interface relies on the Connection: keep-alive header and keep_alive_timeout to maintain persistent sessions. In single-node environments, this mechanism handles basic connection reuse effectively. As deployments scale to distributed clusters, relying on inte
Schema Update Propagation in ReplicatedMergeTree When executing ALTER TABLE ... UPDATE or similar mutations on a ReplicatedMergeTree table across a cluster, ClickHouse manages these changes asynchronously by default. The metadata is propagated via ZooKeeper, but the actual data rewriting occurs in the background as parts are merged. In environments requiring