TiDB to ClickHouse Integration

How Datrise loads TiDB into ClickHouse

Datrise syncs TiDB's tables, rows, schemas, indexes, regions, and TiCDC change events into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

TiDB: MySQL-compatible HTAP database with row and column stores.

ClickHouse: Columnar OLAP engine for fast aggregations.

How TiDB entities map to ClickHouse

TiDB entity	ClickHouse object	Notes
tables	`tidb_tables`	id PK · custom fields → JSON or Map columns
rows	`tidb_rows`	id PK · linked to tidb_tables
schemas	`tidb_schemas`	id PK · linked to tidb_tables
indexes	`tidb_indexes`	id PK · linked to tidb_tables

FAQ

How does Datrise handle TiDB's custom fields in ClickHouse?

Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.

How does the TiDB to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

Connect TiDB to ClickHouse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.