Connector Improvement: Fail Connector If Changes are too big for Teleport instead of Quarantining Silently
Not planned
Previously, we were sync-ing tables using teleport and regardless of the size, teleport sync was attempted and then it could run for a long time and eventually fail.
We see that this behavior has changed. Instead of attempting and failing, the table is now quarantined and removed from the connector schema configuration. This behavior is undesirable and worse than the previous behavior.
There should be an option to configure the connector to fail if this error is encountered instead of quarantining. I think the failure behavior should be the default and not the silent handling/quarantine of the table.
Please see ticket where we first observed this quarantine behavior - pdcc2dbr06 - earnings table is disabled unexpectedly on connector – Fivetran Support
-
Official comment
Hi Joel,
This is a valuable suggestion and I've added the request to our connector improvement backlog. I am curious to learn more about your use case and the specific problems quarantining causes for your workflows. Could you share any additional details on how the silent quarantine impacts your data processes or recovery strategies? Would you like it to fail or try again?
We will keep the community updated on this thread with any progress.
Thanks,
Please sign in to leave a comment.
Comments
1 comment