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 the Bigtable client retries RPC operations."],["The `RPCRetryPolicy` instance is used as a prototype when creating `Table` or `TableAdmin` objects, allowing the creation of new retry policy objects with the same type and initial state."],["The class provides functions like `clone()`, `Setup()`, and `OnFailure()` to manage the retry process, including creating copies, updating the context, and handling failures."],["The `IsExhausted()` method determines whether the retry attempts have been exhausted, and the `IsPermanentFailure()` static methods help determine if an error is permanent."],["The latest version of `RPCRetryPolicy` is 2.37.0-rc, and numerous past versions, starting from 2.11.0, are available on this page."]]],[]]
