Need workaround to make event trigger on Datalake ADLS Gen1

Question

I need to find out a workaround solution to trigger my ADF V2 pipeline when files are placed in data lake ADLS Gen1. So anyone tell me an alternative approach to make a workable solution. Any reference solutions or links are appreciated.

Answer 1

Hi @SimhadriSaripalli-2399,

Welcome to Microsoft Q&A Platform.

Workaround can be to use Azure Functions with Blob Trigger enabled as shown below. Code can be added further into this function according to the requirement once file is read. Please check below useful links as well.

Hope this helps! Do let us know for further queries.

---

Please do consider to click on "Accept Answer" and "Up-vote" on the post that helps you, as it can be beneficial to other community members

Answer 2

One stupid workaround, not sure if that will work for you.

Ask the source team to push dummy.txt file in Gen2 when they push data to Gen1. Create event trigger to point to dummy file in Gen2.

This way, pipeline is triggered as soon as dummy.txt file is created or modified.

===============================================
If the response helped, do "Accept Answer" and upvote it -- Vaibhav

Answer 3

This is a bit of an old question but still seems like the answer is missing. First ADLS gen 1 is not a blob, so you cannot use blob trigger.
What you can do is, set up the diagnostic logging as shown HERE. Feed the logs into an Eventhub. Then have an Azure function listening on the Eventhub link. The Azure function on Consumption plan is needed because it is cheap(it will cheaper than a logic app) and you need to do some filtering. Diagnostic logs will capture a lot of information but you would only want information on when a new file is loaded. When you do get such an event, you can trigger your data factory using the Rest API from Azure function itself Link.