Is there a a chance this can be ommited without any performance and data integrity issues? "*WARNING! Updating the schema will delete all the data for this connection in your destination and start syncing from scratch."* We are a growing startup so sometimes our schema changes and old records get removed, when doing the data reset we can loose records that are present in BQ but no longer present in our database

Yeah, it's less than ideal for sure. We use DBT to transform the data - and we make sure to stage the data in table materializations on top of the airbyte tables. That means that we need to run dbt in order to update the data - but it allows us to update the schema without losing any data (as long as we don't run dbt before airbyte is finished resyncing)

One way you can do (far from ideal) is to use a custom namespace everytime you want to update your schema, this way you're going to save your data in a new schema everytime and have the option to store the old data.

Is there a hope this could be addressed and further releases?