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 page details the `AlwaysRetryMutationPolicy` class within the Google Cloud Bigtable C++ client library, which retries all mutations."],["Using this policy might lead to non-idempotent mutations being resent, potentially resulting in duplicate data with different timestamps."],["The class includes functions to clone the policy (`clone()`) and determine if a mutation is idempotent (`is_idempotent()`)."],["The page lists documentation links for different versions of the library, with version 2.37.0-rc being the latest."],["It shows version 2.14.0 is the version the documentation is currently referencing for detailed information, however, it also lists and references other versions as far back as 2.11.0."]]],[]]
