Does Airbyte handle duplicate records behind the scene for incremental loads? Like if it pulled the record { id: 1 val: my val updated_at: 2020-01-01 } TWICE, will it automatically ignore it the second time? It seems de duplicated handles the scenario where updated_at might change and essentially makes a temporal table... that is not what I am asking Quoting one of the guides: You should see that only the record from the last date is being synced! This is acceptable behavior, since Airbyte requires at-least-once delivery of records, so repeating the last record twice is OK."

This article goes into detail on what happens : https://airbyte.com/tutorials/incremental-data-synchronization

Thanks!