is it possible to have two connections pointed at the same bigquery destination? I need one of them to be full refresh (once per weekend) and the normal one be daily

Yes, it’s possible to have two connections pointing to the same BigQuery destination, but they cannot write to the exact same destination streams (tables) anymore. From Airbyte 1.6 onward, stream identifiers must be unique across all connections that share a destination. You can’t configure multiple connections to sync into the same destination stream (same table name + same namespace), because this can cause job failures and data loss. [[Configuring schemas](https://docs.airbyte.com/platform/using-airbyte/configuring-schema); [Release 1.6 note](https://docs.airbyte.com/release_notes/v-1.6#unique-stream-prefixes-or-namespaces-are-now-mandatory)] To support your use case (one full refresh weekly, one daily incremental/normal): 1. Create two connections that both use the same BigQuery destination. 2. Ensure their destination streams are different by either: - Using different stream prefixes (e.g.

daily_

vs

weekly_

), or - Using different namespaces/datasets in BigQuery. [[Configuring schemas](https://docs.airbyte.com/platform/using-airbyte/configuring-schema)] 3. Configure: - Connection A: your daily sync (incremental or full refresh as needed). - Connection B: your weekend full refresh sync. 4. If you need a single “final” table, merge/combine them downstream in BigQuery (e.g., via views or SQL), which is the recommended pattern. [[Configuring schemas](https://docs.airbyte.com/platform/using-airbyte/configuring-schema)] So: yes, two connections to the same BigQuery destination are fine, as long as they don’t target the same destination stream names; use prefixes/namespaces and then handle consolidation in BigQuery.