No, the removal or addition of a column does not always require a reset, even with the 'propagate column changes only' setting enabled. When a new column is detected and propagated, values for that column will be filled in for the updated rows. If you are missing values for rows not updated, a backfill can be done by completing a full refresh. When a column is deleted, the values for that column will stop updating for the updated rows and be filled with Null values ([source](https://docs.airbyte.com/cloud/managing-airbyte-cloud/manage-schema-changes)). However, if a breaking change is detected, such as the removal of an existing primary key or cursor from the source, the connection will be paused for manual review to prevent future syncs from failing. In such cases, you might need to reset the data ([source](https://docs.airbyte.com/cloud/managing-airbyte-cloud/manage-schema-changes)). Please note that resetting data will delete all records in your destination tables or files, but it will not delete the destination tables or files themselves ([source](https://docs.airbyte.com/operator-guides/reset)).

Yes, you can apply the changes you mentioned without resetting the data. Here's how you can do it: 1. On the [Airbyte Cloud](http://cloud.airbyte.com/) dashboard, click Connections and select the connection where you want to apply the changes. 2. Click Review changes. The Refreshed source schema dialog will display the detected changes. 3. Review the changes and click OK to close the dialog. 4. Scroll to the bottom of the page and click Save changes. When you remove a column, the values for that column will stop updating for the updated rows and be filled with Null values. When you add a column, values for that column will be filled in for the updated rows. If you are missing values for rows not updated, a backfill can be done by completing a full refresh ([source](https://docs.airbyte.com/cloud/managing-airbyte-cloud/manage-schema-changes)). Remember, these steps apply as long as the columns you are adding or removing are not primary keys or cursor fields. If they are, it would be considered a breaking change and the connection will be paused for manual review ([source](https://docs.airbyte.com/cloud/managing-airbyte-cloud/manage-schema-changes)).

I'm sorry to hear that you're experiencing issues. The error message you're seeing suggests that the schema of your source data doesn't match the schema of your destination table in BigQuery. This could happen if the changes in the schema were not propagated as expected. When you add or remove columns without resetting the data, Airbyte should handle these non-breaking changes by filling in new column values for updated rows and filling removed column values with Null for updated rows. However, it seems like this did not happen as expected in your case. Here are a few steps you can take to troubleshoot this issue: 1. Check the logs: The logs provide detailed information about what's happening behind the scenes, and they can help pinpoint the root cause of the problem ([source](https://docs.airbyte.com/troubleshooting)). 2. Review the changes again: Go back to the Connections on the [Airbyte Cloud](http://cloud.airbyte.com/) dashboard and review the changes you made. Make sure the changes were saved correctly. 3. Reach out to the community: If you're still unable to resolve the issue, consider reaching out to the Airbyte community. The community forum is a great place to ask for help, share your experiences, and learn from others who have faced similar issues ([source](https://docs.airbyte.com/troubleshooting)). 4. Open a Github ticket: If you're still unable to resolve the issue after reaching out to the community, it's time to open a support ticket. The Airbyte support team is here to help you with any issues you're facing with Airbyte ([source](https://docs.airbyte.com/troubleshooting)). Remember, it's always a good idea to back up your data and configurations before making changes to your schema or resetting your data.