My MySQL -> Postgres Connection is suddenly not normalizing and transforming the data anymore. It’s only saving the raw data. Why is that?

There could be several reasons why your MySQL to Postgres connection is not normalizing and transforming data anymore. Here are a few possibilities based on the knowledge sources: 1. Connector Version: If you recently upgraded your connector, it's possible that the new version has deprecated the normalization feature. For instance, in one of the [Github issues](https://github.com/airbytehq/airbyte/issues/32288), it was mentioned that Postgres was migrated to a new method, deprecating the normalization. 2. Errors during Sync: Normalization can fail during the sync process due to various reasons such as invalid input syntax for certain data types, connection issues, etc. For example, in one of the [forum posts](https://discuss.airbyte.io/t/2670), the normalization process failed due to "invalid input syntax for type double precision". 3. Deprecated Features: In some cases, features like custom transformation and normalization might have been deprecated. As mentioned in one of the [Github discussions](https://github.com/airbytehq/airbyte/discussions/38168), if you need to use post-transformations to your data, Airbyte recommends using dbt with an orchestrator to run the job to your pipeline. To troubleshoot the issue, you can check the logs for any error messages during the sync process. If the issue persists, consider reaching out to the Airbyte community or support for further assistance.

1. Yeah, I figured. Unfortunately the new version is not working for me. At all. Any way to get the old version with normalization back? Currently I am using the postgres destination 0.6.3. @kapa.ai

Yes, you can roll back to the previous version of the connector if you are encountering issues with the new version. However, please note that this may require clearing each of your upgraded connections. Here are the steps to roll back: 1. In the Airbyte UI, go to the 'Settings' page, then to 'Destinations'. 2. Manually type in the previous destination version you were running. 3. Enter this older version to roll back to the previous connector version. 4. Clear all connections which synced at least once to a previously upgraded destination. To be safe, you may clear all connections sending data to a previously upgraded destination. Please note that if you are hoping to receive support from the Airbyte team, you will need to re-upgrade to Destinations V2 by the upgrade deadline. If you are an Airbyte Cloud customer and encounter errors while upgrading from a V1 to a V2 destination, please reach out to support. For more details, you can refer to the [official documentation](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2#open-source-only-rolling-back-to-legacy-normalization).