copy into doesn't support "safe" implicit conversions from parquet files
currently the copy into command requires datatypes to match exactl.y
when a column is implicitly convertable without a loss of data the import will fail for example if I load a date data type from a parquet file into a datetime or datetime2 the copy into will return an error.
similar behavior exists for decimal datatypes loading into fields with greater scale (goign from 2 decimal points to 5 for example) and loading a non string field into a varchar for example polybase will allow you to load a date field from parquet into a varchar field copy into will fail. all of these scenarios seem valid and should just work to make copy into more robust and developer friendly. Not sure if this issue also impacts ORC files