BlobTrigger in Azure WebJobs does not get triggered on files added after the WebJob is started -


The following problem occurs when the blue operation sample runs from blue-jaboose-sdk-samples (1.0.0-rc1) ().

Bobbrigger runs fine when WebJava starts:

  started the work host: 'Functions. Blobbankformquois 'because new' Qi Messages 'have been detected on individuals Execution:' Functions. Blob twob 'because new drops were detected: Input / Blob operation. Txt executed: 'Functions. BlobTrigger 'because the new drop has been found: Output / Blob Operation. Txt   

but "Input" (or "output") adds some new files to the container after waiting for more than 10 minutes .

When I restart Webb, I uploaded the uploaded files

  public static zero blockbobbob ([blobstritter "input / {name}")] text reader input, [blob (" Output / {Name} ") String Out (Output) {output = input.ReadToEnd (); }   

Samples are using the latest version of the Azure Webjobs SDK:

  & lt; Packages & gt; & Lt; Package id = "Microsoft.Azure.WebJobs" version = "1.0.0-rc1" targetFramework = "net45" /> & Lt; Package ID = "Microsoft.Azure.WebJobs.Core" version = "1.0.0-rc1" targetFramework = "net45" /> & Lt; Package id = "Microsoft.Data.Edm" version = "5.6.0" targetFramework = "net45" /> & Lt; Package id = "Microsoft.Data.odata" version = "5.6.0" targetFramework = "net45" /> & Lt; Package id = "Microsoft.Data.Services.Client" version = "5.6.0" targetFramework = "net45" /> & Lt; Package id = "Microsoft.WindowsAzure.ConfigurationManager" version = "1.8.0.0" targetFramework = "net45" /> & Lt; Package id = "newtonsoft.json" version = "6.0.4" targetFramework = "net45" /> & Lt; Package id = "System.Spatial" version = "5.6.0" targetFramework = "net45" /> & Lt; Package ID = "WindowsAzure.Storage" version = "4.0.1" targetFramework = "net45" /> & Lt; / Packages & gt;   

I have not changed the code of the samples except the location of the package (in my shared space - D: \ Development \ Nuget.Packages) and AzureWebJobsDashboard and AzureWebJobsStorage connection string.

I have the same problem in the 'real' project which is going to go into production.

Is this a bug or am I doing something wrong?

BlobTrigger queue is not instant like SDK Blob scanners scan the container to detect new blogs Or if existing blobs were updated and then the functions of listening to these blobs were triggered. Depending on the size of the container, the scan can take from anywhere to seconds if your app is a requirement for immediate processing, then you should use the queue and then force it to blobs. You can keep the information of the blob such as the container name and the blob name queue message and then use the SDK model binding feature to bind the Blob feature.

Comments

Popular posts from this blog

php - PDO bindParam() fatal error -

logging - How can I log both the Request.InputStream and Response.OutputStream traffic in my ASP.NET MVC3 Application for specific Actions? -

java - Why my included JSP file won't get processed correctly? -