You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2021. It is now read-only.
Feature/can mark processed message complete when exception occurred (#16)
* added support for marking message as proccessed when exception occurred
* Added another test for success or fail as batch
* added comment
* Updated readme file on how to use MarkAsProccess
* updated comment and correct readme format
* Update src/QueueBatch/Impl/Listener.cs
Co-Authored-By: jeremy001181 <[email protected]>
* Update src/QueueBatch.Tests/Helpers.cs
Co-Authored-By: jeremy001181 <[email protected]>
* refactor according the review
Copy file name to clipboardexpand all lines: README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -35,10 +35,10 @@ public static void MyFunc([QueueBatchTrigger("myqueue")] IMessageBatch batch)
35
35
}
36
36
```
37
37
38
-
You can also acknowledge only some of the messages. The rest, will be retried in a similar manner to the regural `[QueueTrigger]`
38
+
With `SuccessOrFailAsBatch` set to `false`, you can also acknowledge only some of the messages. The rest, will be retried in a similar manner to the regural `[QueueTrigger]`
Copy file name to clipboardexpand all lines: src/QueueBatch/QueueBatchTriggerAttribute.cs
+5
Original file line number
Diff line number
Diff line change
@@ -52,5 +52,10 @@ public QueueBatchTriggerAttribute(string queueName)
52
52
/// Gets or sets the app setting name that contains the Azure Storage connection string.
53
53
/// </summary>
54
54
publicstringConnection{get;set;}
55
+
56
+
/// <summary>
57
+
/// If set to false, each message in same batch can be marked as processed independently and they will not affected when other messages cause exception, default to true
0 commit comments