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-05 UTC."],[[["The webpage provides documentation for the `AlwaysRetryMutationPolicy` class in the Google Cloud Bigtable C++ client library, detailing its behavior across multiple versions."],["Version 2.37.0-rc is the latest release candidate, with documentation also available for past versions dating back to 2.11.0, and version 2.36.0 being the currently displayed version."],["The `AlwaysRetryMutationPolicy` retries all mutations, which can lead to non-idempotent mutations being resent and potentially causing multiple entries of the same data with different timestamps."],["The class offers functions such as `clone()` to create copies of the policy and `is_idempotent()` to determine if a mutation or a conditional mutation is idempotent."],["The documentation highlights the constructor for the `AlwaysRetryMutationPolicy`, allowing for instance creation, as well as the implementation of a `std::unique_ptr\u003cIdempotentMutationPolicy\u003e`."]]],[]]
