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, which retries all mutations, potentially leading to non-idempotent operations."],["The latest version of `AlwaysRetryMutationPolicy` is version 2.37.0-rc, with multiple past versions also available, ranging down to version 2.11.0."],["The policy's main functions include `clone()`, `is_idempotent(google::bigtable::v2::Mutation const &)`, and `is_idempotent(google::bigtable::v2::CheckAndMutateRowRequest const &)`, to manage and determine mutation idempotency."],["Using `AlwaysRetryMutationPolicy` with `SetCell()` mutations may create multiple data copies with varying timestamps, so users must handle this potential issue."]]],[]]
