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` class within the Google Cloud Bigtable C++ client library, detailing its role in retrying all mutations."],["The `AlwaysRetryMutationPolicy` may resend non-idempotent mutations, potentially leading to multiple data copies with different timestamps, particularly with `SetCell()` operations where the server determines the timestamp."],["This policy is designed for applications that can manage the consequences of potential duplicate data, such as by querying only the most recent value or employing garbage collection to remove outdated data."],["The class includes functions to check if a mutation is idempotent, `is_idempotent()`, and to return a copy of the policy, `clone()`, and supports different versions of the library all the way from 2.11.0 up to 2.37.0-rc."],["The constructor `AlwaysRetryMutationPolicy()` can be called to utilize this class."]]],[]]
