Continuing sync between Airbyte Cloud and Airbyte OSS for MongoDB to BigQuery replication

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Can a sync started by one instance (Airbyte Cloud) be continued with another instance (Airbyte OSS) for MongoDB to BigQuery replication into the same dataset?


Question

Hey guys, I’m new to Airbyte. I’m trying to sync a few big tables (30 - 200 MB) from MongoDB to BigQuery. The initial replication gets my OSS instance stuck, so I was wondering if I can do the initial replication online and then switch to the OSS. Can I continue the sync started by one instance (i.e. Airbyte Cloud) with another instance (i.e. Airbyte OSS), if they’re syncing into the same dataset?


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.

Join the conversation on Slack

["sync", "airbyte-cloud", "airbyte-oss", "mongodb", "bigquery", "initial-replication", "dataset"]
2

Technically this might be possible if you copy over the current connector state and all the names and other identifiers are the same . . . but it would need to be tested, and may take more effort than fixing whatever resource or config issue is causing your initial sync to fail.