DatriseAI-first ETL

RSS to ClickHouse Integration

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

How Datrise loads RSS into ClickHouse

Datrise syncs RSS's feed items, titles, links, publication dates, authors, and categories 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

RSS: Syndicated feed items from publishers and blogs.

ClickHouse: Columnar OLAP engine for fast aggregations.

How RSS entities map to ClickHouse

RSS entityClickHouse objectNotes
feed itemsrss_feed_itemsid PK · custom fields → JSON or Map columns
titlesrss_titlesid PK · linked to rss_feed_items
linksrss_linksid PK · linked to rss_feed_items
publication datesrss_publication_datesid PK · linked to rss_feed_items

FAQ

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