Airbyte actually does not support this right now. There are some details around how we handle schema and tables names that isn’t going to work for you in the current iteration. If you attempt to do a circular dependency between source and destination, you’ll end up with the following A.public.table_foo writes to B.public.public_table_foo to A.public.public_public_table_foo. You won’t be writing into your original table, which may be your initial intention.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Manage multiple sources sync to the same tables | 1 | 1920 | March 28, 2022 | |
| Support for syncing PostgreSQL foreign table as source to destination | 1 | 55 | June 22, 2024 | |
| Best practices for handling data resets | 4 | 1879 | July 14, 2022 | |
| How does Airbyte handle namespaces (or schemas for the DB-inclined)? | 0 | 527 | September 17, 2021 | |
| Migration from Airbyte 0.50.6 to Airbyte 1.1.0 (OSS) | 0 | 23 | October 30, 2024 |