DatriseAI-first ETL

Elasticsearch to DuckDB Integration

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

How Datrise loads Elasticsearch into DuckDB

Datrise syncs Elasticsearch's indices, documents, mappings, fields, search queries, and aliases 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

Elasticsearch: Search and analytics engine over document indices.

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

How Elasticsearch entities map to DuckDB

Elasticsearch entityDuckDB objectNotes
indiceselasticsearch_indicesid PK · custom fields → JSON or STRUCT columns
documentselasticsearch_documentsid PK · linked to elasticsearch_indices
mappingselasticsearch_mappingsid PK · linked to elasticsearch_indices
fieldselasticsearch_fieldsid PK · linked to elasticsearch_indices

FAQ

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