[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["\u003cp\u003eThis document outlines the \u003ccode\u003eCommitOptions\u003c/code\u003e class, which is used to configure options for calls to \u003ccode\u003espanner::Client::Commit()\u003c/code\u003e, and it is now recommended to use \u003ccode\u003eOptions\u003c/code\u003e instead.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eCommitOptions\u003c/code\u003e allows users to set whether the \u003ccode\u003eCommitResult\u003c/code\u003e should include \u003ccode\u003eCommitStats\u003c/code\u003e, controlling the level of detail returned from commit operations.\u003c/p\u003e\n"],["\u003cp\u003eYou can use \u003ccode\u003eCommitOptions\u003c/code\u003e to set the priority of the commit operation using \u003ccode\u003eset_request_priority\u003c/code\u003e and \u003ccode\u003erequest_priority()\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eset_transaction_tag()\u003c/code\u003e and \u003ccode\u003etransaction_tag()\u003c/code\u003e allow associating a tag with the commit transaction for tracking purposes, but this is ignored if the overload already uses \u003ccode\u003espanner::Transaction\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThere are multiple different versions of \u003ccode\u003eCommitOptions\u003c/code\u003e available to review, with version \u003ccode\u003e2.37.0-rc\u003c/code\u003e being the latest version available.\u003c/p\u003e\n"]]],[],null,[]]