DatriseAI-first ETL

Revinate to DuckDB Integration

AI-first ETL from Revinate into DuckDB. Governed entities, incremental sync, typed landing tables.

How Datrise loads Revinate into DuckDB

Datrise syncs Revinate's guests, reservations, reviews, campaigns, hotels, and guest profiles into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

Revinate: Hospitality guest data and reputation management.

DuckDB: In-process analytics database for fast local OLAP.

How Revinate entities map to DuckDB

Revinate entityDuckDB objectNotes
guestsrevinate_guestsid PK · custom fields → JSON or STRUCT columns
reservationsrevinate_reservationsid PK · linked to revinate_guests
reviewsrevinate_reviewsid PK · linked to revinate_guests
campaignsrevinate_campaignsid PK · linked to revinate_guests

FAQ

How does Datrise handle Revinate's custom fields in DuckDB?

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

How does the Revinate to DuckDB sync stay up to date?

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

Connect Revinate to DuckDB 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.