According to copy-activity-schema-and-type-mapping, it is possible to define the schema for the copy activity. We have been using this process to alter column names in the sink which has been working well. However, we've noticed that all columns are being written to the sink (parquet) as string types, this is causing problems in the subsequent process when trying to write the "string" to a numeric field. To counter that, we've attempted to add the "type" to our mapping definition which caused the failure "Could not load file or assembly '10)' ", the likelihood of the obscure "10), is likely from our type definition being "decimal(18,10)" e.g.
"source": { "name": "EXCHANGE_RATE_DIVISOR" }, "sink": { "name": "EXCHANGE_RATE_DIVISOR", "type": "decimal(18,10)" }
Is this the right way to alter the type?
Should it be on the source or the sink?
What are the correct type definitions?