Summary
User is seeking a method to prevent deleted records in the source MySQL database from being deleted in the destination BigQuery during incremental ingestion with deduplication in Airbyte.
Question
Hi all,
I am reading from a mysql via binlogs and ingesting it incrementally with append and dedup. What we notice is that if a record is deleted in our production db then airbyte will deleted as well from bigquery (where we ingest our data). We are planning to delete some old records from the prod db and we want to keep those records in our bigquery, so I wanted to know if there is a method in airbyte that allow me to keep ingesting incrementally with dedup but not delete record that are deleted in the prod db. Any idea how can I do this with airbyte?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.