[Following material applies to Schedule Triggers in Azure Data Factory. Learn more about Schedule Trigger]
We are really excited to release Time Support for Schedule Trigger in Azure Data Factory. Going forward, you can create schedule triggers in your local time zone, without the need to convert timestamps to Coordinated Universal Time (UTC) first. Furthermore, in this release, we are also adding support for Daylight Saving auto-adjustment: for time zones that observe Daylight Saving, auto change schedule trigger time twice a year (e.g. 8AM daily trigger will fire at 8AM, whether it's PST or PDT)
Note: the changes only apply to new triggers created with time zone other than UTC. Existing ones will continue to follow UTC world clock.
To create a Schedule Trigger in local time zone in UX portal
To create a Schedule Trigger in local time zone with JSON schema
For example, a trigger created in UTC time zone would look like this
{
"properties": {
"name": "MyTrigger",
"type": "ScheduleTrigger",
"typeProperties": {
"recurrence": {
"frequency": "Minute",
"interval": 15,
"startTime": "2017-12-08T00:00:00Z",
"endTime": "2017-12-08T01:00:00Z",
"timeZone": "UTC"
}
},
"pipelines": [{
"pipelineReference": {
"type": "PipelineReference",
"referenceName": "Adfv2QuickStartPipeline"
},
"parameters": {
"inputPath": "adftutorial/input",
"outputPath": "adftutorial/output"
}
}
]
}
}
Some of the time zones we support include:
Time Zone | UTC Offset (Non-Daylight Saving) | timeZone Value | Observe Daylight Saving | Time Stamp Format |
---|---|---|---|---|
Coordinated Universal Time | 0 | UTC |
No | 'yyyy-MM-ddTHH:mm:ssZ' |
Pacific Time (PT) | -8 | Pacific Standard Time |
Yes | 'yyyy-MM-ddTHH:mm:ss' |
Central Time (CT) | -6 | Central Standard Time |
Yes | 'yyyy-MM-ddTHH:mm:ss' |
Eastern Time (ET) | -5 | Eastern Standard Time |
Yes | 'yyyy-MM-ddTHH:mm:ss' |
Greenwich Mean Time (GMT) | 0 | GMT Standard Time |
Yes | 'yyyy-MM-ddTHH:mm:ss' |
Central European Standard Time | +1 | W. Europe Standard Time |
Yes | 'yyyy-MM-ddTHH:mm:ss' |
India Standard Time (IST) | +5:30 | India Standard Time |
No | 'yyyy-MM-ddTHH:mm:ss' |
China Standard Time | +8 | China Standard Time |
No | 'yyyy-MM-ddTHH:mm:ss' |
Fine prints on Monitoring if you programmatically monitor your Schedule Trigger runs: as per usual, trigger time of a schedule trigger run is specified as a UTC timestamp in return value. Please convert to local time zone on client side.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.