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-08-14 UTC."],[[["\u003cp\u003eThe content focuses on the \u003ccode\u003eAlwaysRetryMutationPolicy\u003c/code\u003e class within the Google Cloud Bigtable C++ library, detailing its different versions.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eAlwaysRetryMutationPolicy\u003c/code\u003e will retry all mutations, potentially causing non-idempotent mutations to be resent to the server.\u003c/p\u003e\n"],["\u003cp\u003eThe class includes functions like \u003ccode\u003eclone()\u003c/code\u003e for creating a copy of the policy and \u003ccode\u003eis_idempotent()\u003c/code\u003e to check if a mutation is idempotent.\u003c/p\u003e\n"],["\u003cp\u003eMultiple versions of the \u003ccode\u003eAlwaysRetryMutationPolicy\u003c/code\u003e are available, ranging from 2.11.0 to the latest release candidate 2.37.0-rc, with links to their respective documentation.\u003c/p\u003e\n"],["\u003cp\u003eThere are specific considerations for using this class, for instance the server selecting the timestamp can result in multiple copies of the data stored with different timestamps.\u003c/p\u003e\n"]]],[],null,[]]
