Is there a way to enforce map validation within Pipeline, such that the output of the map could be validated against destination schema and if it does not pass the data type or constraints validation then it throws an error.
I thought this would be a default behaviour, because a map could be tested for any exceptions in Visual Studio. I tried a map between two simple schemas and make it fail by passing string to int data type. It validates fine in Studio but does not do any validation at run time within pipeline.
I have implemented a catch all error orchestration based on promoted error property but if the pipeline does not validate the map output, their will not be any exception and will end up processing bad data.
Is there a solution to this
Thanks
VK