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, which is designed to retry all mutation operations."],["The policy's behavior may lead to non-idempotent mutations being resent, potentially resulting in duplicate data entries with different timestamps, especially with `SetCell()` operations where the server determines the timestamp."],["Users must be aware of potential data duplication issues and implement appropriate handling mechanisms, such as querying for the latest value and setting garbage collection policies."],["The document provides access to various versioned documentation for the `AlwaysRetryMutationPolicy` class, from version 2.11.0 to the latest release candidate, 2.37.0-rc."],["The `AlwaysRetryMutationPolicy` includes functions to check if a mutation or a conditional mutation is idempotent and the ability to create a clone of the policy."]]],[]]
