DatriseAI-first ETL

Selligent ClickHouse

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

How Datrise loads Selligent into ClickHouse

Datrise syncs Selligent's records, events, and configuration objects 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

Selligent: SaaS or API data source for analytics and warehouse sync.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Selligent entities map to ClickHouse

Selligent entityClickHouse objectNotes
recordsselligent_recordsid PK · custom fields → JSON or Map columns
eventsselligent_eventsDateTime64 events
configuration objectsselligent_configuration_objectsid PK · linked to selligent_records

FAQ

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