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 document outlines the `AlwaysRetryMutationPolicy` class within the Google Cloud Bigtable C++ client library, detailing its functionality across various versions."],["The `AlwaysRetryMutationPolicy` retries all mutations, which might lead to duplicate data in cases where the server handles timestamp selection, and it is not recommended for use cases that require no duplicates."],["The policy class provides functions such as `clone()`, `is_idempotent(google::bigtable::v2::Mutation const &)`, and `is_idempotent(google::bigtable::v2::CheckAndMutateRowRequest const &)` for managing and evaluating mutation operations."],["The library supports multiple versions of the Bigtable API, with `2.37.0-rc` currently being the latest release, and version `2.29.0` currently being detailed."]]],[]]
