New Idea
Better Error messaging for failed S3 rules
Currently when an S3 data set task fails for a reason besides the file simply not being present in the S3 bucket, we get an error that reads "Records: -1". This provides no helpful information to the customer to even begin troubleshooting their source file to see what could be missing/misconfigured.
A perfect example was a situation where a customer was trying to push a string value to a number field. With just the error that read "Message: 38, Records: -1", the customer is not offered any direction in what the root issue might be, thus leading to confusion in what to do next.
It would be helpful if we could provide better error messaging in these task failures so that customers can be more enabled to unstand potential issues with S3 data.
A perfect example was a situation where a customer was trying to push a string value to a number field. With just the error that read "Message: 38, Records: -1", the customer is not offered any direction in what the root issue might be, thus leading to confusion in what to do next.
It would be helpful if we could provide better error messaging in these task failures so that customers can be more enabled to unstand potential issues with S3 data.