Hi, does anyone know what I can do when the columns of the target Athena table don't match the S3 CSV file extracted from tap-adwords? extractor: tap-adwords [Report: AD_PERFORMANCE_REPORT] loader: target-athena I'm suspecting this function (generate_column_definitions) from target-Athena somehow reordered the column header because of the schema header value. This causes the data and columns inconsistent issues. A potential solution that I can think of is to add the AD_PERFORMANCE_REPORT schema since tap-adwords has defined 4 schemas already - which are accounts, ad_groups, ads and campaigns. If this is the correct direction, could someone please tell me where I can find the document page of how to add a new schema for the extractor? (I've already dumped the autogenerated catalog JSON locally)