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-14 UTC."],[[["This page details the `RPCRetryPolicy` class in the C++ Bigtable client, which defines the interface for controlling how RPC operations are retried."],["The `RPCRetryPolicy` instance acts as a prototype for creating new retry policy objects with the same type and initial state when a `Table` or `TableAdmin` object is created."],["Key functions within the `RPCRetryPolicy` class include `clone()`, `Setup(grpc::ClientContext &)`, `OnFailure(Status const &)`, and `IsExhausted() const` to manage retry behavior."],["The `IsPermanentFailure` method is used to determine if an error is unrecoverable, which is relevant in helping determine if a retry is worth executing."],["This page provides a list of versions of `RPCRetryPolicy` ranging from the latest release candidate version `2.37.0-rc` down to `2.11.0`, providing easy access to version-specific documentation."]]],[]]
