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 webpage details the `AlwaysRetryMutationPolicy` for Google Cloud Bigtable C++ client library, covering versions from 2.11.0 up to the latest release candidate 2.37.0-rc."],["The `AlwaysRetryMutationPolicy` retries all mutations, which may lead to non-idempotent mutations being resent to the server."],["The policy's implementation allows for mutations like `SetCell()` to create duplicate entries with different timestamps, requiring the application to manage these potential issues, such as by querying for only the latest values."],["The class provides methods to clone the policy (`clone()`) and determine if a given mutation is idempotent (`is_idempotent()`) for both standard and conditional mutations."],["The latest version is 2.37.0-rc, and the page is currently at version 2.34.0, with many prior versions available."]]],[]]
