{"id":2596,"date":"2018-06-21T00:00:00","date_gmt":"2018-06-21T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/event-trigger-based-scheduling-in-azure-data-factory"},"modified":"2023-05-11T15:39:01","modified_gmt":"2023-05-11T22:39:01","slug":"event-trigger-based-scheduling-in-azure-data-factory","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/event-trigger-based-scheduling-in-azure-data-factory\/","title":{"rendered":"Event trigger based data integration with Azure Data Factory"},"content":{"rendered":"

Event driven architecture (EDA) is a common data integration pattern that involves production, detection, consumption and reaction to events. Today, we are announcing the support for event based triggers in your Azure Data Factory<\/a> (ADF) pipelines.<\/p>\n

\n

A lot of data integration scenarios requires data factory customers to trigger pipelines based on events. A typical event could be file landing or getting deleted in your azure storage. Now you can simply create an event based trigger in your data factory pipeline.<\/p>\n

\"image\"<\/p>\n

As soon as the file arrives in your storage location and the corresponding blob is created, it will trigger and run your data factory pipeline. You can create an event based trigger on blob creation, blob deletion or both in your data factory pipelines.<\/p>\n

\"image\"<\/p>\n

With the \u201cBlob path begins with\u201d <\/strong>and \u201cBlob path ends with\u201d<\/strong> properties, you can tell us for which containers, folders, and blob names you wish to receive events. You can also use wide variety of patterns for both \u201cBlob path begins with\u201d<\/strong> and \u201cBlob path ends with\u201d<\/strong> properties. At least, one of these properties is required.<\/p>\n

\"image\"<\/p>\n

Examples:<\/p>\n