@kapa.ai after upgrading the redshift connector to 4.0.2, is it safe to get rid of the airbyte_internal schema?

Based on the knowledge sources, yes — after upgrading to Redshift destination version 4.0.0+, raw tables (

_airbyte_raw_*

) are no longer created, so the

airbyte_internal

schema is no longer used by the connector. [Redshift Output Schema] The migration guide explicitly states: > Raw tables (

_airbyte_raw_*

) are no longer produced... Optional: Drop old raw tables (

_airbyte_raw_*

) after verifying the new tables. [Redshift Migration Guide] Before dropping the

airbyte_internal

schema, make sure to: 1. Verify that your data in the final tables looks correct after the upgrade. 2. Confirm that no downstream dbt models or SQL queries still reference the old raw tables in

airbyte_internal

. 3. Ensure all your connections have completed at least one successful sync with the new 4.0.x connector. Once those checks pass, it is safe to drop the old

airbyte_internal

schema (or just the raw tables within it). [Redshift Migration Guide] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

ok, what I mean is that I'm getting updates on mysql that are not being catpured by airbyte and redshift is missing them