Specifies the status of an insert attempt depending on the validity of the rows.
Note that the validity of a row is determined by whether AllowUnknownFields
is set to true or not.
If AllowUnknownFields is set to true, then rows containing fields
that do not match any on the destination table will, otherwise, be considered valid rows.
All matching fields in these rows will be inserted, while unmatching fields will be silently skipped.
If AllowUnknownFields is not set to true, then rows containing fields
that do not match any on the destination table will be considered invalid and won't be inserted.
All rows were inserted successfully.
This only happens if all rows are valid rows.
NoRowsInserted
No rows were inserted. In that case the BigQueryInsertResults
returned by the insert operation will contain error information about the invalid rows.
This can happen when:
No rows are valid.
SkipInvalidRows is not set to true and at least
one row is invalid.
SomeRowsInserted
Some rows were inserted but not others. In that case the BigQueryInsertResults
returned by the insert operation will contain error information about the rows that were not inserted.
This happens only when SkipInvalidRows is set to true and some,
but not all of the rows, are invalid.
[[["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-07 UTC."],[[["\u003cp\u003eThis document outlines the \u003ccode\u003eBigQueryInsertStatus\u003c/code\u003e enum, which tracks the success of row insertion attempts into a BigQuery table.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version of the API is 3.11.0, but this document also contains information about previous versions, starting with 2.2.0.\u003c/p\u003e\n"],["\u003cp\u003eRow validity is determined by the \u003ccode\u003eAllowUnknownFields\u003c/code\u003e setting, where \u003ccode\u003etrue\u003c/code\u003e allows unmatched fields to be skipped and \u003ccode\u003efalse\u003c/code\u003e results in the row being considered invalid.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eBigQueryInsertStatus\u003c/code\u003e enum can have three possible values: \u003ccode\u003eAllRowsInserted\u003c/code\u003e, \u003ccode\u003eNoRowsInserted\u003c/code\u003e, or \u003ccode\u003eSomeRowsInserted\u003c/code\u003e, each indicating the success of row insertions.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eSkipInvalidRows\u003c/code\u003e option will impact the \u003ccode\u003eBigQueryInsertStatus\u003c/code\u003e with some rows inserted if set to true, otherwise no rows will be inserted if at least one is invalid.\u003c/p\u003e\n"]]],[],null,[]]
