Site feedback

JinleiWang-5017 avatar image
0 Votes"
JinleiWang-5017 suggested JinleiWang-5017 edited

The official documentation should be able to explicitly state what data is expected to be able to be transferred without truncation/loss of fidelity in ADF

If this is explicitly an issue with the capabilities of the destination file type, that the following articles would benefit from having a “known limitations” section added for the limitations in precision of the supported data types:

https://docs.microsoft.com/en-us/azure/data-factory/format-avro#avro-as-sink
https://docs.microsoft.com/en-us/azure/data-factory/format-orc#orc-as-sink

If however there are more general issues with data type translation between Source > Interim, or Interim > Sink, then it would be useful to have a list of known limitations updated in the existing data type mapping article:

https://docs.microsoft.com/en-us/azure/data-factory/copy-activity-schema-and-type-mapping#data-type-mapping


There is much better to discover that data is being truncated or otherwise modified through trial and error in ADF pipeline.

adfs
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

No Solutions

Your Opinion Counts

Share your feedback, or help out by voting for other people's feedback.