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, focusing on its behavior across different versions, including the latest version 2.37.0-rc."],["The `AlwaysRetryMutationPolicy` retries all mutations, which may cause non-idempotent mutations to be re-sent and potentially result in multiple entries with different timestamps, requiring special handling by the application."],["The policy provides a `clone()` function to create a copy of the policy, and `is_idempotent()` functions to determine if a mutation or conditional mutation is idempotent."],["This documentation covers version 2.11.0 up to the most recent, version 2.37.0-rc, with 27 versions listed in total."]]],[]]
