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 document outlines the `AlwaysRetryMutationPolicy` for Google Cloud Bigtable C++ client library, covering versions from 2.11.0 to the latest release candidate 2.37.0-rc."],["The `AlwaysRetryMutationPolicy` will retry all mutations, which may lead to non-idempotent mutations being resent and potentially creating multiple entries with different timestamps, particularly with `SetCell()` operations."],["Users should exercise caution and only use this policy if their application can handle duplicate data entries or if they are applying strategies such as garbage collection to eliminate old values."],["The class provides methods to check if a mutation or conditional mutation is idempotent, with `is_idempotent` returning a boolean value, and a `clone()` function returning a unique pointer to a copy of the policy."],["The `AlwaysRetryMutationPolicy` has one constructor, `AlwaysRetryMutationPolicy()` with no parameters, along with two functions, `virtual clone()` and `virtual is_idempotent()`."]]],[]]
