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 document details the `RPCRetryPolicy` class in the C++ Bigtable client, which defines the interface for controlling how the client retries RPC operations."],["The `RPCRetryPolicy` allows users to manage the number of retry attempts, the frequency of these attempts, and how to signal errors, providing flexibility for handling partial and temporary failures."],["The `clone()` function in this class is used to create new instances of the same retry policy, while `Setup()` updates the `ClientContext` for the next call."],["`OnFailure` is used to handle RPC failures, and determine whether the RPC operation should be retried or not."],["The `IsPermanentFailure` static method, identifies whether a given status, either `Status` or `grpc::Status`, indicates a permanent failure."]]],[]]
