den_usenko
08/04/2021, 1:43 PMProvided Schema does not match Table when I edit 'select' section in meltano.yml.
Is there a way to recreate one specific table on the next run of meltano elt with new settings and keep other tables and their incremental state intact?douwe_maan
08/04/2021, 2:06 PMIs there a way to recreate one specific table on the next run of meltano elt with new settings and keep other tables and their incremental state intact?Manually running
meltano elt <tap> <target> --select=<stream/table> --full-refresh --job_id=<job_id> should do the trick. That run should reload stream, and subsequent runs should use the combined state of that run and the earlier incremental onesden_usenko
08/04/2021, 2:10 PMpipelinewise-tap-mysql and target-bigquerydouwe_maan
08/04/2021, 2:12 PMselect config in meltano.yml? Do the names you’re using there match what you see in meltano select <tap> --list --all?den_usenko
08/04/2021, 2:47 PMselect config is fine and the problem is on the target-bigquery side.
I've added few new fields to select (--list --all shows tables I need and the '*' symbol does the job right) and got error 400: Provided Schema does not match Table.
Before your response I've deleted the table in question manually in BigQuery to get rid of mismatch situation. That helped. On the next elt run this table was created from scratch.
Example of my selects:
select:
- '*a_users_orders.orders_id'
- '*a_users_orders.users_id'
- '*a_users_orders.orders_paid'
In my case, adding a few more lines like this caused an error.
I expected full table reset (drop and create with new set of fields) in case of schema mismatch, but probably that's just out of the scope of elt job :)douwe_maan
08/04/2021, 3:07 PM