Connector Improvement: Historical syncs of new tables cause delay of active tables (Active tables should be synced first!)
Answered
Our daily sync is delayed on multiple days because new tables (added to the connector) need to sync historical data. Unfortunately, this historical sync precedes the sync of our active tables resulting in very unnecessary delays of our important data, affecting our business. It is totally obvious: The active (relevant) tables should be synced before the historical sync of the (yet irrelevant) new tables. The current order makes no sense.
-
Official comment
Thank you Purelei,
We are aware of this issue and are working on a technical design to address this. The issue is currently that our system considers all the tables within a connection to be part of a single "sync job". In order to fix this, we need to break this up into multiple jobs so that incremental workloads can proceed without being blocked by historical workloads. Expect to see a fix for this released later this year.
Please sign in to leave a comment.
Comments
1 comment