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."],[[["This page provides documentation for the `PermanentMutationFailure` class within the Google Cloud Bigtable C++ client library, spanning multiple versions."],["The class `PermanentMutationFailure` is designed to handle and report unrecoverable errors that occur during a partially completed mutation."],["The class has constructors that allow the creation of `PermanentMutationFailure` objects using parameters like error message (`msg`), status (`grpc::Status`), and a vector of mutation failures."],["The `failures()` function returns detailed information about each mutation failure, which is essential for applications needing to respond to specific problems."],["The `status()` function allows you to check the overall status of the request, which may still return `grpc::Status::OK` even if partial failures occur during `BulkApply()`."]]],[]]