DatriseAI-first ETL

Younium to ClickHouse Integration

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

How Datrise loads Younium into ClickHouse

Datrise syncs Younium's subscriptions, accounts, invoices, products, orders, and usage records 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

Younium: B2B subscription management and recurring billing.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Younium entities map to ClickHouse

Younium entityClickHouse objectNotes
subscriptionsyounium_subscriptionsid PK · custom fields → JSON or Map columns
accountsyounium_accountsid PK · linked to younium_subscriptions
invoicesyounium_invoicesid PK · linked to younium_subscriptions
productsyounium_productsid PK · linked to younium_subscriptions

FAQ

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