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` for Google Cloud Bigtable C++ client library, specifically within the context of version 2.28.0."],["The `AlwaysRetryMutationPolicy` implements a strategy to retry all mutations, which may lead to non-idempotent mutations being resent, potentially resulting in multiple data copies with different timestamps."],["This policy is designed for scenarios where applications can handle potential data duplication, such as only retrieving the most recent value or using garbage collection to remove old data."],["The policy offers methods to clone the policy, determine if a single mutation is idempotent and determine if a conditional mutation is idempotent."],["The page also provides a comprehensive list of links to the documentation for the `AlwaysRetryMutationPolicy` across different versions of the library ranging from 2.11.0 to the latest release candidate 2.37.0-rc."]]],[]]
