Summary
Sync from Stripe to Redshift failing due to drop_cascade configuration parameter. Concerns about cascading deletion of destination tables and impact on views built on top of them.
Question
Hello! Our Stripe->Redshift destination sync is failing with Failure in destination: Failed to drop table without the CASCADE option. Consider changing the drop_cascade configuration parameter. We can change that parameter, but are slightly concerned — we build views on top of the destination tables. Are the destination tables being cascading deleted, or just some temporary ones? Is there a way to avoid deleting destination tables?
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.