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-04-17 UTC."],[[["This webpage details the `AlwaysRetryMutationPolicy` for Google Cloud Bigtable in C++, which retries all mutations."],["Using this policy may result in non-idempotent mutations being resent, potentially causing data duplication with different timestamps, especially with `SetCell()` mutations."],["The `AlwaysRetryMutationPolicy` includes functions to determine if a mutation or a conditional mutation (`CheckAndMutateRowRequest`) is idempotent, as well as a method to create a copy of the policy."],["The page provides a list of links to different versions of the documentation, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc, offering historical and current version access."]]],[]]
