Horia
12/03/2025, 10:04 AMkapa.ai
12/03/2025, 10:05 AMDROP ... CASCADE with your current configuration. Two key points from the docs: 1. Airbyte sometimes drops and recreates final tables (“soft reset”) for schema migrations or transactional full refreshes. If you have modified those final tables (e.g., added constraints, sort keys, or other dependencies), this can cause drop failures during those operations. [[Typing & deduping](https://docs.airbyte.com/platform/using-airbyte/core-concepts/typing-deduping#on-final-table-re-creation)] 2. Redshift destination has a drop_cascade option. When dependent objects exist, Airbyte needs DROP ... CASCADE to succeed; without it, you get exactly the error you’re seeing. [[Redshift reference](https://docs.airbyte.com/integrations/destinations/redshift#reference)] Recent Redshift destination versions explicitly added support to respect this option for raw tables as well. [[Redshift changelog](https://docs.airbyte.com/integrations/destinations/redshift#changelog)] Why it “suddenly” started happening: - A connector or platform upgrade may have triggered a soft re‑creation of your tables, or changed how drops are issued. - Someone may have added dependent objects (views, constraints, or Redshift sort/dist settings tied to Airbyte columns) on those tables since your earlier successful syncs, so the same drop operation that used to work now fails. How to resolve: 1. Option A (recommended when you can safely recreate dependent objects): - Enable “Drop tables with CASCADE” (drop_cascade) in your Redshift destination settings so Airbyte can drop and recreate tables that have dependents. [[Redshift reference](https://docs.airbyte.com/integrations/destinations/redshift#reference)] - Be aware this will also drop any dependent views/objects; you should have automation (e.g., dbt) to recreate them. [[Creating dependent objects](https://docs.airbyte.com/integrations/destinations/redshift#creating-dependent-objects)] 2. Option B (if you cannot use CASCADE): - Manually remove or adjust the dependent objects on the failing table (e.g., drop or change views/constraints/sort-key usage that block the drop), then rerun the sync. The knowledge sources don’t give specific Redshift DDL examples here, but the principle is to ensure the Airbyte-managed table can be dropped without CASCADE. If after enabling drop_cascade or removing dependents you still see the error, the knowledge sources do not provide additional Redshift‑specific troubleshooting steps beyond these configuration and dependency checks.