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 page details the `AlwaysRetryMutationPolicy` for Google Cloud Bigtable C++ client library, specifically within the context of version 2.22.1."],["The `AlwaysRetryMutationPolicy` implements a strategy to retry all mutations, which may lead to non-idempotent mutations being resent."],["Using this policy may result in multiple copies of data with different timestamps when retrying `SetCell()` mutations where the server determines the timestamp, requiring application-level handling."],["The `AlwaysRetryMutationPolicy` includes functions such as `clone()` to create a copy of the policy, and `is_idempotent()` to check if a given mutation or conditional mutation is idempotent."],["The latest version of the `AlwaysRetryMutationPolicy` is `2.37.0-rc`, with a list of previous versions from `2.36.0` down to `2.11.0` also provided."]]],[]]
