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 within the Google Cloud Bigtable C++ client, outlining how it manages retries for RPC operations."],["The `RPCRetryPolicy` class offers users control over the number and frequency of retry attempts for operations, as well as when to signal an error."],["Users provide an instance of `RPCRetryPolicy` when creating `Table` or `TableAdmin` objects, which serves as a template for creating new `RPCRetryPolicy` objects with the same dynamic type and initial state."],["Key functions of the `RPCRetryPolicy` include `clone()`, `Setup()`, and `OnFailure()`, which are used for copying the object, updating the `ClientContext`, and handling RPC failures respectively."],["The page lists all available versions of the `RPCRetryPolicy` class, from 2.11.0 all the way up to 2.37.0-rc."]]],[]]
