Cosmos DB: Add retry policy support for Cosmos DB Trigger#798
Merged
Cosmos DB: Add retry policy support for Cosmos DB Trigger#798
Conversation
alrod
approved these changes
Sep 15, 2022
Member
|
Is |
Member
Author
Yep. |
brettsam
approved these changes
Sep 20, 2022
This was referenced Sep 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds
[SupportsRetry]decorator to the Trigger Binding to allow users to define retry policies. This would bring the Cosmos DB Trigger among the ones (Kafka, Timer, Event Hub) that will keep having Retry Policy support.This support will be included in the
4.Xversion of the extension.Closes Azure/azure-cosmos-dotnet-v3#3437
Related to #783