In airbyte if we keep on changing the source repeatedly in the one single connection, is it recommendable

Airbyte's approach to handling changes in the source schema is to continue syncing data using the configured schema until that schema is updated. If a field is renamed or deleted in the source, that field will no longer be replicated, but all remaining fields will continue to be. The schema can only be updated manually in the UI by clicking “Update Schema” in the settings page for the connection. When a schema is updated, Airbyte will re-sync all data for that source using the new schema. However, it's important to note that changing the source schema frequently could lead to issues. For instance, if you're using Airbyte's full refresh synchronization modes, repeatedly syncing an entire source table that contains a large amount of data or data that is frequently synchronized may become infeasible. In such cases, other replication modes may be more appropriate. Also, if you're using tabular destinations, they should be consistent in how they handle schema evolutions over the period of a connection’s lifecycle, including gracefully handling expected organic schema evolutions, such as the addition of new columns after the initial sync. In conclusion, while it's technically possible to keep changing the source in a single connection, it's not generally recommended due to potential issues with data synchronization and schema evolution. It's advisable to plan your data integration strategy carefully to minimize the need for frequent source changes. Sources: - [Full Data Synchronization](https://airbyte.com/tutorials/full-data-synchronization#step-9) - [Requirements for Airbyte Partner Connectors](https://docs.airbyte.com/connector-development/partner-certified-destinations#exceptions) - [Forum Post: How does Airbyte handle replication when a data source changes its schema?](https://discuss.airbyte.io/t/90)