Apologize for all the questions but everyone has been very helpful. Does anyone have experience changing schema with the

target-bigquery

plugin? When I make a change to the source

tap-postgres

I'm getting the following error

BadRequest: 400 Provided Schema does not match Table

I was hoping schema changes would not cause ELT failure and it would either ignore the new column or add it on the next run. Does anyone know if this is possible?

@matt_hardner We're doing office hours now, feel free to join us and ask the question there 🙂 https://meltano.slack.com/archives/C01QS0RV78D/p1622044826012500 We can debug this together

@douwe_maan Thanks for the time during office hours. Changing the pip_url to

@development

fixed several issues. The truncate functionality now works and schema changes are automatically applied to bigquery. You need to have replication_method set to truncate for this to happen or else you get the same

BadRequest: 400

@matt_hardner That's great! I hope they'll release the development branch soon, but it sounds like it could still take another month: https://github.com/adswerve/target-bigquery/issues/9#issuecomment-825816630