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` for Google Cloud Bigtable C++ client library, which is designed to retry all mutations, including non-idempotent ones."],["The latest version of the library documented is 2.37.0-rc, and versions as far back as 2.11.0 are included in the documentation."],["The policy may cause non-idempotent mutations, such as `SetCell()` with server-selected timestamps, to result in multiple data copies with varying timestamps, which could cause storage issues if the problem is not handled on the application side."],["The `AlwaysRetryMutationPolicy` class offers functions to check if a mutation is idempotent and has a method to clone the policy."],["The AlwaysRetryMutationPolicy constructor is also included in the documentation."]]],[]]
