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-05-07 UTC."],[[["This document outlines the `AlwaysRetryMutationPolicy` for Google Cloud Bigtable C++ client library, with the latest version being 2.37.0-rc."],["The `AlwaysRetryMutationPolicy` is designed to retry all mutations, which may lead to non-idempotent mutations being resent."],["The policy's behavior can result in issues like multiple data entries with different timestamps in cases like `SetCell()` mutations if the server chooses the timestamp."],["The `AlwaysRetryMutationPolicy` class provides functions like `clone()` to create copies of the policy and `is_idempotent()` to check if a mutation is idempotent, for both general mutations and conditional row mutations."],["This document covers version history for this class dating back to version 2.11.0."]]],[]]
