New fields (3) will only be merged in once (1) and (2) are done and merged into master.
Additional notes for this PR:
I need to update the Hauser documentation and the changes can be best summarized by -
The application relies on clients not renaming existing hauser exported column names.
If we find that a column is missing in an existing export table (either because we added new fields or a client deleted an existing schema column), we execute alter table statements and add in the missing columns.
If there are extra columns present on the export table, we only populate the columns whose name matches with the export schema. Indirectly we are relying on any other columns on the table to be nullable.
This PR makes it so the export to Redshift works if changes are made to the export table client side, or if new fields are added to the export.
This is part (1) of a larger arc of work which will - (1) Add support for changing export schema on Redshift (2) Add support for changing export schema on BigQuery (3) Add new fields to the export
New fields (3) will only be merged in once (1) and (2) are done and merged into master.
Additional notes for this PR: I need to update the Hauser documentation and the changes can be best summarized by -