ADF COPY无法更改管道中的默认活动时间 [英] ADF COPY Can't change defaulted Activity times in Pipeline

问题描述

当从SQL Server VM到Azure SQL数据库中创建ADF COPY时，COPY管道的开始时间为6:00 am.但是，它生成的最终脚本增加了活动时间，这意味着COPY活动在欧洲中部时间00:00(格林尼治标准时间1:00)运行.

这是为什么，我该如何更改?

我尝试了几件事，但是基本上没有地方可以在创建向导中添加各个活动时间"或偏移".

还，一旦您进入JSON脚本，如果在Pipeline脚本中添加偏移量或时间更改，则它会抱怨它在 与输出数据集冲突( ).

但是如果您更改了Output Dataset脚本，则表示不允许这样做( .

下面是Pipeline脚本中的一个片段，显示了活动时间段.

欢迎提出任何建议，并在此先感谢

开始":"2018-09-06T06:00:00Z"，跨度>

"结束":"2019-12-31T00:00:00Z""，

" isPaused":false，

" runtimeInfo"":{

     部署时间":"2018-09-07T13:30:35.9855693Z"，

    "activePeriodSetTime":"2018-09-07T13:30:36.5535017Z"，

    "pipelineState":正在运行"，

    "activityPeriods":{

        " activity-0- [stg_schema] _ [Table1]-> [target_schema] _ [ 表1 ]" ;: {

           开始":"2018-09-06T00:00:00Z"，

           结束":"2019-12-31T00:00:00Z"

       }，

        ‘activity-1-[ stg_schema Table2 ]-> [ target_schema 表2

           开始":"2018-09-06T00:00:00Z"，

           结束":"2019-12-31T00:00:00Z"

       }，

        ‘activity-2-[ stg_schema 表3 ]-> [ target_schema 表3

           开始":"2018-09-06T00:00:00Z"，

           结束":"2019-12-31T00:00:00Z"

解决方案

似乎更新可用性的问题仍然没有解决.

https://feedback.azure.com/forums/270578-data-factory/suggestions/13115547-azure-data-factory-add-ability-to-update-dataset

我能想到的解决方法是使用克隆"功能.按钮来复制另一个数据集，并更改管道以引用新数据集.

您还可以考虑使用ADF V2.它提供了易于理解和使用的滚动窗口触发器和计划触发器.

https://docs.microsoft.com/zh-cn/azure/data-factory/how-to-create-tumbling-window-trigger

https://docs.microsoft.com/zh-cn/azure/data-factory/how-to-create-schedule-trigger

When creating an ADF COPY from a SQL Server VM into an Azure SQL Database, The COPY pipeline had a start time of 6:00am. However, the final script it generated adds activity periods meaning the COPY activities run at 00:00 CET (1:00 GMT).

Why is this and how can I change it ?

I tried a few things but basically there is nowhere to add individual Activity times or an Offset in the creation wizard.

Also, once you get into JSON scripts, if you add an Offset or time change to the Pipeline script then it complains that it is in conflict with the Output Dataset (The Activity schedule does not match the schedule of the output Dataset. Activity: 'StoredProcedureActivityTemplate'. Dataset: 'OutputDatasetStoPro'.).

But if you change the Output Dataset script then it says that it is not allowed to do that (Updating the availability section of a Dataset is not supported).

Below is a snipit from the Pipeline script showing the activity periods.

Any advice is welcome and thanks in advance.

"start": "2018-09-06T06:00:00Z",

"end": "2019-12-31T00:00:00Z",

"isPaused": false,

"runtimeInfo": {

    "deploymentTime": "2018-09-07T13:30:35.9855693Z",

    "activePeriodSetTime": "2018-09-07T13:30:36.5535017Z",

    "pipelineState": "Running",

    "activityPeriods": {

        "activity-0-[stg_schema]_[Table1]->[target_schema]_[Table1]": {

            "start": "2018-09-06T00:00:00Z",

            "end": "2019-12-31T00:00:00Z"

        },

        "activity-1-[stg_schema]_[Table2]->[target_schema]_[Table2]": {

            "start": "2018-09-06T00:00:00Z",

            "end": "2019-12-31T00:00:00Z"

        },

        "activity-2-[stg_schema]_[Table3]->[target_schema]_[Table3]": {

            "start": "2018-09-06T00:00:00Z",

            "end": "2019-12-31T00:00:00Z"

解决方案

Hi,

Seems the issue of updating the availability is still not fixed. 

https://feedback.azure.com/forums/270578-data-factory/suggestions/13115547-azure-data-factory-add-ability-to-update-dataset

A workaround I can come up with is to use the "clone" button to duplicate another dataset and change your pipeline to reference the new dataset. 

And you could also consider to use ADF V2. It provides tumbling window trigger and schedule trigger which are easy to understand and use. 

https://docs.microsoft.com/en-us/azure/data-factory/how-to-create-tumbling-window-trigger

https://docs.microsoft.com/en-us/azure/data-factory/how-to-create-schedule-trigger

这篇关于ADF COPY无法更改管道中的默认活动时间的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！