Airbyte creates the tables in the destination, or this is a manual task?

Airbyte, not Airflow, is responsible for creating tables in the destination. This process is automatic and not a manual task. During a sync operation, Airbyte may drop and re-create the final table produced by a sync, sometimes referred to as a "soft reset". This is done for a number of reasons, including schema migrations and transactional full refreshes. In some cases, you might need to manually trigger a final table re-creation, for example, if you accidentally delete some records from the final table and want to repopulate them from the raw data. This can be done by dropping the final table, unsetting the raw table's

_airbyte_loaded_at

column, and then running a sync. After the sync completes, your final table will be restored to its correct state. Here is the process for manually triggering a final table re-creation: 1. Drop the final table entirely (

DROP TABLE <your_final_table>

) 2. Unset the raw table's

_airbyte_loaded_at

column (

UPDATE airbyte_internal.<your_raw_table> SET _airbyte_loaded_at = NULL

) 1. If you are using a nonstandard raw table schema, replace

airbyte_internal

with that schema. 3. Run a sync. After the sync completes, your final table will be restored to its correct state. For more details, you can refer to the [Airbyte documentation](https://docs.airbyte.com/using-airbyte/core-concepts/typing-deduping#on-final-table-re-creation).