Rki Covid → DuckDB
AI-first ETL from Rki Covid into DuckDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads Rki Covid into DuckDB
Datrise syncs Rki Covid's records, events, and configuration objects 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
Rki Covid: SaaS or API data source for analytics and warehouse sync.
DuckDB: In-process analytics database for fast local OLAP.
How Rki Covid entities map to DuckDB
| Rki Covid entity | DuckDB object | Notes |
|---|---|---|
| records | rki_covid_records | id PK · custom fields → JSON or STRUCT columns |
| events | rki_covid_events | TIMESTAMP WITH TIME ZONE events |
| configuration objects | rki_covid_configuration_objects | id PK · linked to rki_covid_records |
FAQ
How does Datrise handle Rki Covid'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 Rki Covid 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
More destinations for Rki Covid
Early access
Connect Rki Covid 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.