Let's say I statically define a schema - it will fix the optional fields. In a few months, the API Vendor introduces a new field and I doing a select *, it will miss data where that field is being populated. For me in this scenario I'm incrementally ingesting 100,000's of records on a daily basis - it is likely to matter if I find this later on. I wonder if we could optionally have the pipeline fail if it detects a record being emitted and a field wasn't in the schema. This would give you an opportunity to fix the schema and re-start the process? Currently it is just a warning in the Meltano Log.