Dremio to Supabase Integration

How Datrise loads Dremio into Supabase

Datrise syncs Dremio's datasets, tables, reflections, query jobs, sources, and table schemas into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Dremio: Lakehouse query engine over open table formats.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Dremio entities map to Supabase

Dremio entity	Supabase object	Notes
datasets	`dremio_datasets`	id PK · custom fields → jsonb columns
tables	`dremio_tables`	id PK · linked to dremio_datasets
reflections	`dremio_reflections`	id PK · linked to dremio_datasets
query jobs	`dremio_query_jobs`	id PK · linked to dremio_datasets

FAQ

How does Datrise handle Dremio's custom fields in Supabase?

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

How does the Dremio to Supabase sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Dremio to Supabase 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.