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-07-09 UTC."],[[["This document details the `RPCBackoffPolicy` class within the Google Cloud Bigtable C++ client, which manages how the client handles failed RPC operations."],["The `RPCBackoffPolicy` allows users to configure the number of retries, the timing between retries, and how to signal errors, providing flexibility in error management for Bigtable operations."],["When creating `Table` or `TableAdmin` objects, users must provide an instance of this `RPCBackoffPolicy` class, which acts as a prototype for new objects."],["The class provides functions such as `clone()`, `Setup()`, and multiple `OnCompletion()` overloads, to create copies, set up client context, and define retry delay respectively."],["The document lists available versions, including version 2.37.0-rc as the latest version, and lists other previous versions all the way down to version 2.11.0."]]],[]]
