Summary
When dealing with large datasets in Airbyte connectors, is it possible to force incremental updates to start from a specific date/time by adjusting the index/state flags?
Question
Hey all - hoping you can help! We have a number of connectors running in our own hosted AirByte to a Snowflake destination. The destination database parameter was changed by mistake and our data was being pushed into a different Snowflake database for a few days. We have updated the destination back to the correct destination now. For a some of the connectors we have run a resync in the correct destination, however there are a few datasets that are very large and we want to avoid full re-sync. Is there any way that we force the incremental updates to start from a set date/time by adjusting the index/state flags? <@U06AC8ZCLUF>
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.