Notice that this will may result in non-idempotent mutations being resent to the server. Re-trying a SetCell() mutation where the server selects the timestamp can result in multiple copies of the data stored with different timestamps. Only use this policy if your application is prepared to handle such problems, for example, by only querying the last value and setting garbage collection policies to delete the old values.
[[["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 `AlwaysRetryMutationPolicy` class within the Google Cloud Bigtable C++ client library, specifically for version 2.23.0 and onwards."],["The `AlwaysRetryMutationPolicy` will retry all mutations, which may lead to non-idempotent operations being resent to the server, resulting in multiple copies of data with different timestamps."],["This class includes a constructor, a `clone()` function to create a copy of the policy, and `is_idempotent()` functions to check if a mutation or conditional mutation is idempotent."],["The document provides a list of available versions of this class, ranging from 2.11.0 to the latest release candidate, 2.37.0-rc."]]],[]]
