Geek Answers Handbook

Azure Functions: Configure blob to run only for new events

I have about 800k blobs in my azure vault. When I create the azure function using blobTrigger, it starts to process all the drops that I have in the repository. How to configure the function to run only for new and updated blobs?

+8
c # azure azure-storage-blobs azure-functions
source share
2 answers

There is currently no way to do this. Inside, we track which drops we processed by storing receipts in our azure-webjobs-hosts management container. Any blob that does not have a receipt or an old receipt (based on an ETag blob) will be processed (or recycled). That's why your existing drops are processed - they have no receipts. BlobTrigger is currently designed to ensure that ALL drops in the container that match the path pattern are ultimately processed and processed at any time when they are updated.

If you are passionate about this, you can register a feature request in our repo here with detailed information about your script.

+6
source share

Has anyone found some workaround for this? I'm currently trying to use BlobTrigger in Azure Functions to handle SQL audit logs.

I only need new magazines that go forward, but we have a rather high storage period, so viewing all of these blobs with NOOP (in several environments and receipts for each host, too) seems very slow / for that.

0
source share

More articles:


All Articles