Skippr Docs

Appearance

How to Review ClickHouse Warehouse Config Before Production ​

July 2026

ClickHouse is ready for production only when the write path and the read model are both understood, especially the delayed merge behavior behind final-state CDC.

Short Answer ​

Review a ClickHouse warehouse config by checking url, database, user, and password, then validating the CDC read model the docs describe. Production readiness here is not only about writing rows successfully. It is also about confirming that the team understands ClickHouse final-state reconciliation through ReplacingMergeTree semantics, where recent duplicate versions can be visible until merges finish.

That distinction matters immediately. A setup that writes to http://clickhouse.internal:8123 as skippr_writer into database: raw can still create confusion if analysts expect every query to show instant in-place replacement. The CDC destination docs are clear that Skippr records _skippr_order_token values and tombstones, but ClickHouse may still need FINAL for correctness-sensitive reads right after fresh mutations.

Why Teams Struggle with This ​

Teams often review ClickHouse like a conventional MERGE-first warehouse and only later discover that the read model needs its own checklist. The connector can be working correctly while recent duplicate versions are still visible before background merges finish.

  • The ClickHouse user needs write access to the target database and tables over the documented HTTP interface.
  • A successful load does not mean all fresh reads will look deduplicated immediately.
  • Production consumers need to understand when FINAL is required for point-in-time correctness.
  • CDC review should include both order-token and tombstone behavior, because delete safety is separate from version deduplication.

How Skippr Handles It ​

Skippr keeps the warehouse surface straightforward with a URL, database, user, and password, which is useful because it leaves room to review the more important question: whether ClickHouse is the right final-state read model for this team.

The CDC contract is explicit rather than magical. Skippr writes versioned rows, manages _skippr_order_token columns and tombstone tables, and depends on ClickHouse merge behavior instead of pretending the platform acts like an immediately updating row store.

  • Writes to ClickHouse over HTTP with a small connector surface.
  • Uses ReplacingMergeTree-based final-state CDC reconciliation.
  • Creates order-token columns and tombstone tables automatically.
  • Supports fresh correctness-sensitive reads through FINAL when needed.

What the First Useful Version Looks Like ​

The first useful version is one database, one CDC-managed table, and one query check that compares a normal read with a FINAL read after recent updates.

If the team does not want to own that read-model explanation, review whether another warehouse destination would be easier to support before production.