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-21 UTC."],[[["This webpage details the `AlwaysRetryMutationPolicy` class within the Google Cloud Bigtable C++ client library, specifically for version 2.16.0 and other listed versions."],["The `AlwaysRetryMutationPolicy` retries all mutations, which may lead to non-idempotent mutations being resent to the server and potential data duplication in certain scenarios."],["The class includes methods to clone the policy (`clone()`) and check if a mutation or a conditional mutation is idempotent (`is_idempotent()`)."],["The listed documentation displays the class across multiple versions, ranging from the latest release candidate (2.37.0-rc) down to version 2.11.0, including release versions such as 2.16.0 and 2.25.1."]]],[]]
