make microbatch strategy support insert-by-name #1338
Description
Describe the feature
recent adapter additions brought insert-by-name behavior to some processes that do not natively support it, see here and here. one place that is still lacking that behavior is the microbatch strategy. microbatch models still break upon column order change (unless the data types still match, then it will silently produce wrong data).
Describe alternatives you've considered
add complex validation that detects and alerts when code schema and database schema do not align for microbatch models.
Additional context
dealing with column order is so annoying that, for us, this is seen as a blocker for migrating insert_overwrite models to microbatch
Who will this benefit?
clients that have large incremental models suitable for microbatch, who do not want to deal with the frequent issues that arise from column order mismatches.
Are you interested in contributing this feature?
potentially ;)