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 page documents the `AlwaysRetryMutationPolicy` class within the Google Cloud Bigtable C++ client library, detailing its functionality across multiple versions, from 2.11.0 up to the latest release candidate 2.37.0-rc."],["The `AlwaysRetryMutationPolicy` implements a strategy to retry all mutations, which may result in non-idempotent mutations being resent to the server and creating possible issues, so caution should be taken."],["The class provides two key functions, `clone()`, which creates a copy of the policy, and `is_idempotent()`, which determines if a given mutation or conditional mutation is idempotent, returning a boolean in each case."],["The `AlwaysRetryMutationPolicy` constructor `AlwaysRetryMutationPolicy()` is also a part of the class."],["This class and its corresponding functions are available in all versions of the Bigtable C++ library that are listed."]]],[]]
