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 document details the `RPCRetryPolicy` class in the Google Cloud Bigtable C++ client, which manages how the client retries RPC operations to hide partial and temporary failures."],["The `RPCRetryPolicy` class is used as a prototype when creating `Table` or `TableAdmin` objects, allowing the application to control the frequency and number of retry attempts."],["Key functions within `RPCRetryPolicy` include `clone()`, `Setup()`, and `OnFailure()`, which respectively create copies of the policy, update the client context, and handle RPC failures to determine if a retry is necessary."],["The class also provides methods like `IsExhausted()` to check if the retry limit has been reached, and `IsPermanentFailure()` to determine if an error should not be retried."],["The latest version of this document is for the release candidate 2.37.0-rc, and there are listed links for prior releases starting with 2.36.0 down to 2.11.0."]]],[]]
