Implement per-method retry policies#643
Open
tescherm wants to merge 1 commit into
Open
Conversation
tescherm
force-pushed
the
configurable-retries
branch
from
d569ca1 to
9608db2
Compare
Contributor
Author
|
@gkousik please have a look |
Contributor
Author
|
@ywmei-brt1 @bentekkie @fitzner please have a look |
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
1 participant
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.
Previously, the client used a single global Retrier for all RPC calls.
This PR adds support for specifying per-method retry policies, allowing users to override the default retrier for specific RPCs (e.g.,
ExecuteAndWait). This implementation follows the existing pattern used for per-method timeouts (RPCTimeouts).