When to use Tumbling Window type trigger

Priya Jha 871 Reputation points
2020-12-22T13:03:11.23+00:00

Hi All,

Was going through Microsoft document on Triggers available in ADF.
Can anyone explain what is the significance of Tumbling Window Trigger type as we can add recurrence in Schedule trigger type too then in what scenario should we use Tumbling Window?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,681 questions
0 comments
Accepted answer
  1. Vaibhav Chaudhari 38,736 Reputation points
    2020-12-22T15:15:40.603+00:00

    Use TWT when you have to pull data generated in specific time interval, say - pull the files uploaded in Azure storage between 2PM to 3PM, then 3PM to 4PM and so on... TWT allows you to use start time and end time which can be used to filter the source data based on generation time. It can also be used to backfill the data.

    Detailed use case is given here - https://www.cathrinewilhelmsen.net/2019/12/12/triggers-azure-data-factory/

    Please don't forget to Accept Answer and Up-vote if the response helped -- Vaibhav

    7 people found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Nasreen Akter 10,791 Reputation points
    2020-12-22T13:37:09.52+00:00

    Hi @Priya Jha ,

    Tumbling window trigger is a type of trigger that fires at periodic time intervals from a specified start time. Tumbling windows are a series of fixed-sized, non-overlapping and contiguous time intervals. Important difference between a schedule trigger and a tumbling window trigger are:

    • A schedule trigger can only trigger future dated loads. But tumbling window triggers can be configured to initiate past and future dated loads.
    • Schedule pipelines and triggers have a many-to-many relationship. Whereas a tumbling window trigger has a one-to-one relationship with a pipeline and can only reference a single pipeline.
    • Tumbling window trigger has a self-dependency property which means the trigger shouldn't proceed to the next window until the preceding window is successfully completed.

    Hope this helps. If it does, please don't forget to "accept the answer" and "up-vote"! Thank you!

    Useful links:
    https://video2.skills-academy.com/en-us/azure/data-factory/tumbling-window-trigger-dependency
    https://www.mssqltips.com/sqlservertip/6061/create-tumbling-window-trigger-in-azure-data-factory-adf/

    27 people found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.