Error returned when problems were encountered. If present, it indicates rows were not accepted into the system. Users can retry or continue with other append requests within the same connection. Additional information about error signalling: ALREADY_EXISTS: Happens when an append specified an offset, and the backend already has received data at this offset. Typically encountered in retry scenarios, and can be ignored. OUT_OF_RANGE: Returned when the specified offset in the stream is beyond the current end of the stream. INVALID_ARGUMENT: Indicates a malformed request or data. ABORTED: Request processing is aborted because of prior failures. The request can be retried if previous failure is addressed. INTERNAL: Indicates server side error(s) that can be retried.
If backend detects a schema update, pass it to user so that user can use it to input new type of message. It will be empty when no schema updates have occurred.
If a request failed due to corrupted rows, no rows in the batch will be appended. The API will return row level error info, so that the caller can remove the bad rows and retry the request.
↳ write_stream
string
The target of the append operation. Matches the write_stream in the corresponding request.
Error returned when problems were encountered. If present,
it indicates rows were not accepted into the system.
Users can retry or continue with other append requests within the
same connection.
Additional information about error signalling:
ALREADY_EXISTS: Happens when an append specified an offset, and the
backend already has received data at this offset. Typically encountered
in retry scenarios, and can be ignored.
OUT_OF_RANGE: Returned when the specified offset in the stream is beyond
the current end of the stream.
INVALID_ARGUMENT: Indicates a malformed request or data.
ABORTED: Request processing is aborted because of prior failures. The
request can be retried if previous failure is addressed.
INTERNAL: Indicates server side error(s) that can be retried.
Error returned when problems were encountered. If present,
it indicates rows were not accepted into the system.
Users can retry or continue with other append requests within the
same connection.
Additional information about error signalling:
ALREADY_EXISTS: Happens when an append specified an offset, and the
backend already has received data at this offset. Typically encountered
in retry scenarios, and can be ignored.
OUT_OF_RANGE: Returned when the specified offset in the stream is beyond
the current end of the stream.
INVALID_ARGUMENT: Indicates a malformed request or data.
ABORTED: Request processing is aborted because of prior failures. The
request can be retried if previous failure is addressed.
INTERNAL: Indicates server side error(s) that can be retried.
If backend detects a schema update, pass it to user so that user can
use it to input new type of message. It will be empty when no schema
updates have occurred.
If backend detects a schema update, pass it to user so that user can
use it to input new type of message. It will be empty when no schema
updates have occurred.
If a request failed due to corrupted rows, no rows in the batch will be
appended. The API will return row level error info, so that the caller can
remove the bad rows and retry the request.
If a request failed due to corrupted rows, no rows in the batch will be
appended. The API will return row level error info, so that the caller can
remove the bad rows and retry the request.
[[["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-09-04 UTC."],[],[],null,["# Google BigQuery Storage V1 Client - Class AppendRowsResponse (2.1.5)\n\nVersion latestkeyboard_arrow_down\n\n- [2.1.5 (latest)](/php/docs/reference/cloud-bigquery-storage/latest/V1.AppendRowsResponse)\n- [2.1.4](/php/docs/reference/cloud-bigquery-storage/2.1.4/V1.AppendRowsResponse)\n- [2.0.0](/php/docs/reference/cloud-bigquery-storage/2.0.0/V1.AppendRowsResponse)\n- [1.10.4](/php/docs/reference/cloud-bigquery-storage/1.10.4/V1.AppendRowsResponse)\n- [1.9.0](/php/docs/reference/cloud-bigquery-storage/1.9.0/V1.AppendRowsResponse)\n- [1.8.0](/php/docs/reference/cloud-bigquery-storage/1.8.0/V1.AppendRowsResponse)\n- [1.7.1](/php/docs/reference/cloud-bigquery-storage/1.7.1/V1.AppendRowsResponse)\n- [1.6.0](/php/docs/reference/cloud-bigquery-storage/1.6.0/V1.AppendRowsResponse)\n- [1.5.0](/php/docs/reference/cloud-bigquery-storage/1.5.0/V1.AppendRowsResponse)\n- [1.4.1](/php/docs/reference/cloud-bigquery-storage/1.4.1/V1.AppendRowsResponse)\n- [1.3.2](/php/docs/reference/cloud-bigquery-storage/1.3.2/V1.AppendRowsResponse)\n- [1.2.12](/php/docs/reference/cloud-bigquery-storage/1.2.12/V1.AppendRowsResponse) \nReference documentation and code samples for the Google BigQuery Storage V1 Client class AppendRowsResponse.\n\nResponse message for `AppendRows`.\n\nGenerated from protobuf message `google.cloud.bigquery.storage.v1.AppendRowsResponse`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ BigQuery \\\\ Storage \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getAppendResult\n\nResult if the append is successful.\n\n### hasAppendResult\n\n### setAppendResult\n\nResult if the append is successful.\n\n### getError\n\nError returned when problems were encountered. If present,\nit indicates rows were not accepted into the system.\n\nUsers can retry or continue with other append requests within the\nsame connection.\nAdditional information about error signalling:\nALREADY_EXISTS: Happens when an append specified an offset, and the\nbackend already has received data at this offset. Typically encountered\nin retry scenarios, and can be ignored.\nOUT_OF_RANGE: Returned when the specified offset in the stream is beyond\nthe current end of the stream.\nINVALID_ARGUMENT: Indicates a malformed request or data.\nABORTED: Request processing is aborted because of prior failures. The\nrequest can be retried if previous failure is addressed.\nINTERNAL: Indicates server side error(s) that can be retried.\n\n### hasError\n\n### setError\n\nError returned when problems were encountered. If present,\nit indicates rows were not accepted into the system.\n\nUsers can retry or continue with other append requests within the\nsame connection.\nAdditional information about error signalling:\nALREADY_EXISTS: Happens when an append specified an offset, and the\nbackend already has received data at this offset. Typically encountered\nin retry scenarios, and can be ignored.\nOUT_OF_RANGE: Returned when the specified offset in the stream is beyond\nthe current end of the stream.\nINVALID_ARGUMENT: Indicates a malformed request or data.\nABORTED: Request processing is aborted because of prior failures. The\nrequest can be retried if previous failure is addressed.\nINTERNAL: Indicates server side error(s) that can be retried.\n\n### getUpdatedSchema\n\nIf backend detects a schema update, pass it to user so that user can\nuse it to input new type of message. It will be empty when no schema\nupdates have occurred.\n\n### hasUpdatedSchema\n\n### clearUpdatedSchema\n\n### setUpdatedSchema\n\nIf backend detects a schema update, pass it to user so that user can\nuse it to input new type of message. It will be empty when no schema\nupdates have occurred.\n\n### getRowErrors\n\nIf a request failed due to corrupted rows, no rows in the batch will be\nappended. The API will return row level error info, so that the caller can\nremove the bad rows and retry the request.\n\n### setRowErrors\n\nIf a request failed due to corrupted rows, no rows in the batch will be\nappended. The API will return row level error info, so that the caller can\nremove the bad rows and retry the request.\n\n### getWriteStream\n\nThe target of the append operation. Matches the write_stream in the\ncorresponding request.\n\n### setWriteStream\n\nThe target of the append operation. Matches the write_stream in the\ncorresponding request.\n\n### getResponse"]]
