Non-Incremental Sync for Large Data Volume

Summary

Non-incremental sync to address cursor value irrelevance and performance impact of refetching large data volume


Question

I’m guessing that a non-incremental sync would fix the issues (due to the cursor value becoming irrelevant) but this would be pretty taxing to completely refetch ~150k records per sync



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.

Join the conversation on Slack

["non-incremental-sync", "cursor-value", "large-data-volume", "performance"]