U-SQL错误调试 [英] U-SQL error debugging

问题描述

是否有一种很好的方法来判断U-SQL作业顶点中的哪个文件实际上导致了错误?我一直找不到简单的方法，几个月来一直让我发疯.例如，我在Data Lake中有一份包含1,000多个文本文件的工作 得到处理.如果其中一个文件中的行中有一个错误的值，则该作业将失败，但是没有简单的方法来判断是哪个文件导致了该失败.它会显示Vertix ...._ Split [0] [887]错误，但是没有简单的方法可以知道是哪个文件. 因此，我必须尝试在1,000多个文件中手动找到该文件.这非常耗时.

Is there a good way to tell which file within the U-SQL job vertex actually caused an error? I have not been able to find an easy way and it has been driving me mad for months.  For instance, I have a job with over 1,000 text files in the Data Lake that get processed.  If there's a bad value in a row in one of the files the job fails but there is no easy way to tell which file caused the failure.  It gives a Vertix...._Split[0][887] error, but there's no easy way to tell which file that means.  So I have to try and manually find the file within the 1,000+ files.  This is very time consuming.

是否有一种简单的方法来查找错误的文件并进行记录?如果没有，我建议将导致错误的文件从数据"标签中的其他文件中分离出来.这不应该是一个很难添加的功能，并且可以节省大量的时间. 时间疑难解答错误. 

Is there an easy way to find the bad file and record?  If not, I would recommend singling the file that caused the error out from the other files in the Data tab.  This shouldn't be a hard feature to add and would save a considerable amount of time troubleshooting errors. 

推荐答案

您是否有机会在此论坛中提及对feedback.azure.com创建反馈

did you get a chance to create a feedback on feedback.azure.com as mentioned in this forum thread?

这篇关于U-SQL错误调试的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！