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 document outlines the `AlwaysRetryMutationPolicy` class within the Google Cloud Bigtable C++ client library, detailing its functionality across various versions."],["The `AlwaysRetryMutationPolicy` retries all mutations, which could lead to duplicate data with different timestamps if the server selects the timestamp during a `SetCell()` operation."],["The class provides a `clone()` function to create copies of the policy and `is_idempotent()` functions to determine if mutations or conditional mutations are idempotent."],["The document lists available versions of this function ranging from version 2.11.0 all the way up to the most recent release candidate 2.37.0-rc."]]],[]]
