@kapa.ai Why is my MongoDB to BigQuery connection writing to

airbyte_internal

instead of the destination I defined ? (ie

my_destination

)

This is expected behavior in Airbyte's Destinations V2 architecture. Airbyte writes data to two locations: 1. Raw tables in the

airbyte_internal

schema — these are internal staging tables used by Airbyte as part of the Typing and Deduping process. 2. Final tables in your configured destination schema (e.g.,

my_destination

) — these are the typed, deduplicated tables intended for your use. The

airbyte_internal

schema is where Airbyte stores raw, unprocessed data before transforming it into the final tables in your destination. [Destinations V2 upgrade] As noted in the BigQuery destination behavior, Airbyte produces "raw tables" by default in the

airbyte_internal

schema, and it is not recommended to interact directly with these raw tables, as their format is subject to change. [Databricks output schema] Your actual data should be available in the final tables within your configured destination dataset (

my_destination

). If you are not seeing data there, it may indicate a sync issue rather than a misconfiguration. > Note: The knowledge sources do not contain specific documentation for the MongoDB-to-BigQuery connector combination, so if the final tables are missing entirely, I'd recommend checking your sync logs for errors or reaching out to Airbyte support. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.