DatriseAI-first ETL

Dixa ClickHouse

AI-first ETL from Dixa into ClickHouse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Dixa into ClickHouse

Datrise syncs Dixa's conversations, agents, customers, tags, and resolution metrics 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

Dixa: Customer service platform for conversations across channels.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Dixa entities map to ClickHouse

Dixa entityClickHouse objectNotes
conversationsdixa_conversationsid PK · custom fields → JSON or Map columns
agentsdixa_agentsid PK · linked to dixa_conversations
customersdixa_customersid PK · linked to dixa_conversations
tagsdixa_tagsid PK · linked to dixa_conversations

FAQ

How does Datrise handle Dixa'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 Dixa 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 Dixa 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.