ingestr recipes/Load a specific sourceData Engineer

How do I keep a database table in sync without full reloads (CDC-style)?

Use an incremental key with the merge strategy so ingestr only moves changed rows on each run. You get change-aware replication into your warehouse without hand-writing merge logic or standing up a CDC service.

Command

ingestr ingest

Defined in

CLI

Works with

Any ingestr source and destination

What you get

Change-aware loadsincremental keymerge strategy

How it works in code

$ ingestr ingest \
  --source-uri $SRC --source-table 'public.events' \
  --dest-uri $DST --dest-table 'raw.events' \
  --incremental-strategy merge --incremental-key updated_at

Run ingestr ingest and ingestr moves only the rows that changed since the last run.

Move data with one command

Open source. Source URI in, destination URI out, incremental by default.

Sign up to our newsletter

Practical updates on open-source data pipelines, AI analysts, governance, and what we are shipping at Bruin.

The signup form is hosted by Brevo. Accept cookies to load it.