if i was using incremental dedup mode and there are some records that got deleted at source, does airbyte delete them or would stay in the destination?

In standard Incremental | Append + Deduped mode (without CDC), deleted records from the source are not propagated to the destination — they will remain in the destination table. [Incremental Append docs] This happens because incremental sync selects records by querying the source for rows that have been inserted or modified since the last sync. Deleted records simply don't appear in that query, so Airbyte has no way to know they were removed. [Incremental sync tutorial] Your options to handle deletions 1. Use CDC (Change Data Capture): If your source supports CDC (e.g., PostgreSQL, MySQL with CDC enabled), Airbyte can capture delete events and propagate them to the destination. With CDC + Deduped mode, deleted records are actually removed from the final destination table. [CDC tutorial] 2. Use Full Refresh Overwrite: This completely replaces the destination table with the current source data on every sync, so deletions are naturally reflected. The downside is it re-syncs all data every time. 3. Soft Deletes: If your source marks deleted records with a flag (e.g.,

is_deleted = true

) rather than physically removing them, incremental sync can pick up that change and reflect it in the destination. [Incremental sync tutorial] In summary, if you need deletions to be reflected in the destination, CDC replication is the recommended approach. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.