Because BulkApply() and Apply() take ownership of the data in the mutations the failures are returned with their full contents, in case the application wants to take further action with them. Any successful mutations are discarded.
Any mutations that fail with an unknown state are included with a grpc::StatusCode::OK.
Returns
Type
Description
std::vector< FailedMutation > const &
status() const
The grpc::Status of the request.
Notice that it can return grpc::Status::OK when there are partial failures in a BulkApply() operation.
[[["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."],[[["The page provides documentation for the `PermanentMutationFailure` class within the Google Cloud Bigtable C++ library, detailing its structure and functionality."],["This class is used to report errors that occur during partial or failed mutations within the Bigtable database."],["The class's functions include `failures()`, which returns details of the failed mutations, and `status()`, which provides the `grpc::Status` of the request, which could show partial failure when the `grpc::Status` is `grpc::Status::OK`."],["There are several versions of the `PermanentMutationFailure` class are documented, ranging from version `2.11.0` to `2.37.0-rc` (the latest release candidate)."],["The `PermanentMutationFailure` has two constructors that accept a message and a vector of failed mutations, but one of them also takes a `grpc::Status`."]]],[]]
