通过跳过不兼容的行来进行复制活动中的容错 [英] Fault tolerance in Copy Activity by skipping incompatible rows

查看:91
本文介绍了通过跳过不兼容的行来进行复制活动中的容错的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我将Azure Fucntion与Azure SDK和Azure Data Factory一起使用,在复制活动中应用记录不兼容的行"时,有什么方法可以获取活动窗口的skippedRowCount 的值(来源:Blob存储) ,接收器:SQL数据仓库)?

I use Azure Fucntion with Azure SDK and Azure Data Factory, is there any way to get value of skippedRowCount of Activity Window when applying "log the incompatible rows" in Copy Activity (Source: Blob Storage, Sink: SQL Data Warehouse)?

推荐答案

从此处的文档中: https://[您的blob帐户] .blob.core.windows.net/[路径是否已配置]/[copy-activity-run-id]/[自动生成的GUID] .csv .您可以设置 blob触发器在生成的日志文件上.这是一个示例function.json

From the documentation here : Monitor skipped rows, looks like a log file is automatically generated when log incompatible rows is enabled at https://[your-blob-account].blob.core.windows.net/[path-if-configured]/[copy-activity-run-id]/[auto-generated-GUID].csv. You can set up a blob trigger on the generated log file. Here is a sample function.json

"disabled": false,
"bindings": [
    {
        "name": "myBlob",
        "type": "blobTrigger",
        "direction": "in",
        "path": "[path-if-configured]/[copy-activity-run-id]",
        "connection":"MyStorageAccountAppSetting"
    }
]

注意:您还可以使用

Note: you could also use blob name patterns to specify path in the binding.

在功能代码中,您可以轻松访问日志文件的内容以获取skippedRowCount

In the function code, you can easily access the contents of the log file to get the skippedRowCount

这篇关于通过跳过不兼容的行来进行复制活动中的容错的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆