Define the interface for controlling how the Bigtable client retries RPC operations.
The C++ client for Bigtable needs to hide partial and temporary failures from the application. However, we need to give the users enough flexibility to control how many attempts are made to reissue operations, how often these attempts are executed, and how to signal that an error has occurred.
The application provides an instance of this class when the Table (or TableAdmin) object is created. This instance serves as a prototype to create new RPCRetryPolicy objects of the same (dynamic) type and with the same initial state.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This webpage provides documentation for the `RPCRetryPolicy` class in the Google Cloud Bigtable C++ client library, offering versioned references."],["The `RPCRetryPolicy` class defines how the Bigtable client handles retries of RPC operations, allowing control over the number of attempts, frequency, and error signaling."],["Users create an instance of `RPCRetryPolicy` when constructing `Table` or `TableAdmin` objects, serving as a template for creating new retry policy objects."],["The `RPCRetryPolicy` includes methods like `clone()`, `Setup()`, `OnFailure()`, and `IsExhausted()` to manage retry behavior and interact with `grpc::ClientContext` and `Status` objects."],["The webpage further includes static functions such as IsPermanentFailure to determine if a failure is permanent and Type Aliases such as `RetryableTraits` for internal safe grpc retry usage."]]],[]]
