Has the way Airbyte ingests data changed recently? I made a connection from MySQL to Snowflake. It no longer ingests the raw data into the destination schema but into a new schema 'airbyte_internal' that it creates. ANd even though I select the transformation as 'Raw JSON', it loads a normalized table structure in the destination schema. What has changed and why?

Hmm, I don't know enough to give you a confident answer yet. The extracts provided do not contain information about recent changes to the way Airbyte ingests data or about the creation of a new schema 'airbyte_internal'. However, based on the information available, Airbyte follows an ELT (Extract, Load, Transform) process. In this process, raw data is first loaded into a destination and then goes through a transformation stage. If you have Basic Normalization enabled, Airbyte automatically uses this JSON blob to create a schema and tables with your data in mind, converting it to the format of your destination. This runs after your sync and may take a long time if you have a large amount of data synced. If you don't enable Basic Normalization, you'll have to transform the JSON data from that column yourself [[source]](https://docs.airbyte.com/understanding-airbyte/basic-normalization/). For destinations that support normalization, SQL is then executed to transform the raw JSON back into a relational table. Internally Airbyte leverages dbt to create the SQL used for normalizing and/or transforming data [[source]](https://airbyte.com/tutorials/full-data-synchronization). For more specific information about recent changes or about the 'airbyte_internal' schema, I would recommend checking the official Airbyte documentation or reaching out to the Airbyte community.