42 results · 0.031s
Docs
Configuring an incremental sync
Choose a cursor column, set the batch size, and let the first run establish a watermark. An incremental sync reads only rows changed since that point.
docs / sources / syncs·Updated 12 Aug
Docs
Updated recentlyCursor columns and watermarks
Every incremental sync stores a watermark. Choosing an unindexed column is the most common reason a sync times out.
docs / sources / cursors·Updated 16 Aug
Article
Backfilling without melting production
The trick is to treat the backfill as an incremental sync that happens to start from zero, with the same checkpoints and the same rate limits.
journal / migrations·26 Jun
Video
Setting up your first sync (4:12)
Walks through a full incremental sync against a Postgres source, including what to do when the preview returns nothing.
videos / getting-started·04 May
Changelog
Updated recentlyv4.2 — faster cursors and composite watermarks
An incremental sync can now use two columns as a composite watermark, which fixes ties on identical timestamps.
changelog / 4.2·02 Aug