Improve ClickHouse

Operation

Implement the requested coherent change at the owning source and update directly affected consumers. An earlier audit is optional when the user and repository already establish the target. Validate the changed behavior, then stop when the requested scope is complete.

Goal

Implement one selected, evidence-backed ClickHouse improvement at the authoritative owner. Complete the directly affected contract without broad cleanup or redesign.

Domain rules

• Choose engine/partition/ORDER BY from concrete access and lifecycle patterns; avoid high-cardinality partitions and broad FINAL as a routine correctness fix.
• Make ingestion idempotency explicit with stable source identity and supported dedup semantics; do not rely on a short dedup window for indefinite retries.
• Rewrite queries to prune early, bound joins/aggregations/results, and use projections/dictionaries/materialized views only with owned refresh/consistency semantics.
• Stage schema/view/backfill changes and throttle mutations or rebuilds; preserve compatibility for existing parts and distributed replicas.
• Set users, quotas, profiles, pools, and workload limits from aggregate deployment capacity and expose system-table signals.

Validation

• Run DDL/query/ingestion integration tests against the supported ClickHouse version/topology and inspect system tables/query logs.
• Exercise duplicate/retried batches, partial failure, late data, replica/distributed-queue disruption, merge pressure, mutation/backfill, and query concurrency.
• Measure scanned rows/bytes, memory/spill, parts, merge backlog, insert/query latency, and result correctness with representative data shape.