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."],[[["The latest version of the `AlwaysRetryMutationPolicy` is 2.37.0-rc, with a full list of available versions ranging from this to 2.11.0."],["This policy retries all mutations, which may lead to non-idempotent mutations being resent to the server and potential duplicate data with differing timestamps."],["The policy's use is only recommended if the application can manage issues stemming from the described behavior such as querying only the last value and employing garbage collection policies."],["It includes methods like `clone()`, `is_idempotent(google::bigtable::v2::Mutation const &)`, and `is_idempotent(google::bigtable::v2::CheckAndMutateRowRequest const &)` to manage policy copies and assess mutation idempotency."]]],[]]
