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. Bruin does this in one platform: ingestion, SQL and Python pipelines, quality checks, lineage, and an AI data analyst that answers in Slack, Microsoft Teams, and the browser.
Command
ingestr ingestDefined 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_atRun ingestr ingest and ingestr moves only the rows that changed since the last run.
Related use cases
Load a specific source
Replicate a Postgres database into Snowflake
How do I replicate a Postgres database into Snowflake?
Load a specific sourceLoad Google Sheets into your warehouse
How do I load a Google Sheet into my warehouse?
Load a specific sourceLoad Stripe data into your warehouse
How do I load Stripe data into my warehouse?
Move data with one command
Open source. Source URI in, destination URI out, incremental by default.