@kapa.ai If I have run a sync into a given namespace/schema (so I have something like “dataset.table1”) if I then change the destination namespace (so like “dataset2.table1"), will the next sync need to re-scan the entire source table1 in order to push into this “new” schema?

Yes, if you change the destination namespace, the next sync will need to re-scan the entire source table to push into this "new" schema. This is because Airbyte treats the change in namespace as a new destination, and it doesn't have a mechanism to track the changes between different namespaces. In the context of incremental sync modes, you would need to copy the raw data you've already replicated to the new schema being used by your newly created connection. This needs to be done for every stream in the connection with an incremental sync mode. You can use SQL to do this in your data warehouse. After that, you need to navigate to the existing connection you are duplicating, and navigate to the

Settings

tab. Open the

Advanced

settings to see the connection state (which manages incremental syncs). Copy the state to your clipboard. Please note that if you are using the same table name from different sources, you should change the namespace (schema), or the table when setting up the syncs so they don't collide. A common pattern is

${source_name}_${table_name}

, so you'll end up with

pg1_customers

and

pg2_customers

. Sources: - [Upgrading to Destinations V2](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2#additional-steps-for-incremental-sync-modes) - [Github Issue Comment](https://github.com/airbytehq/airbyte/issues/30531)