Define the interface for controlling how the Bigtable client backsoff from failed 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 RPCBackoffPolicy 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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["This document details the `RPCBackoffPolicy` class within the Google Cloud Bigtable C++ client library, which manages backoff strategies for failed RPC operations."],["The `RPCBackoffPolicy` class provides users flexibility in controlling the number of retry attempts, the frequency of those attempts, and how errors are signaled."],["The class offers methods like `clone()`, `Setup(grpc::ClientContext &)`, and `OnCompletion(Status const &)` for creating copies, configuring the client context, and determining the delay after a failed operation, respectively."],["The application will provide an instance of this class when the Table (or TableAdmin) object is created, to define the initial state and dynamic type."],["This documentation lists the available versions of the RPCBackoffPolicy class from version 2.11.0 up to the latest version."]]],[]]
