Get desktop application:
View/edit binary Protocol Buffers messages
BigQuery request and response messages for audit log. Note: `Table.schema` has been deprecated in favor of `Table.schemaJson`. `Table.schema` may continue to be present in your logs during this transition.
Request data for each BigQuery method.
Table insert request.
Table update request.
Dataset list request.
Dataset insert request.
Dataset update request.
Job insert request.
Job query request.
Job get query results request.
Table data-list request.
Response data for each BigQuery method.
Table insert response.
Table update response.
Dataset insert response.
Dataset update response.
Job insert response.
Job query response.
Job get query results response.
Deprecated: Job query-done response. Use this information for usage analysis.
A job completion event.
An access control list.
Used in:
Access control entry list.
Access control entry.
Used in:
The granted role, which can be `READER`, `WRITER`, or `OWNER`.
Grants access to a group identified by an email address.
Grants access to a user identified by an email address.
Grants access to all members of a domain.
Grants access to special groups. Valid groups are `PROJECT_OWNERS`, `PROJECT_READERS`, `PROJECT_WRITERS` and `ALL_AUTHENTICATED_USERS`.
Grants access to a BigQuery View.
BigQuery dataset information. See the [Dataset](/bigquery/docs/reference/v2/datasets) API resource for more details on individual fields.
Used in:
, , ,The name of the dataset.
User-provided metadata for the dataset.
The time the dataset was created.
The time the dataset was last modified.
The access control list for the dataset.
If this field is present, each table that does not specify an expiration time is assigned an expiration time by adding this duration to the table's `createTime`. If this field is empty, there is no default table expiration time.
User-provided metadata for a dataset.
Used in:
A short name for the dataset, such as`"Analytics Data 2011"`.
A long description, perhaps several paragraphs, describing the dataset contents in detail.
Dataset insert request.
Used in:
The dataset to be inserted.
Dataset insert response.
Used in:
Final state of the inserted dataset.
Dataset list request.
Used in:
Whether to list all datasets, including hidden ones.
The fully-qualified name for a dataset.
Used in:
, ,The project ID.
The dataset ID within the project.
Dataset update request.
Used in:
The dataset to be updated.
Dataset update response.
Used in:
Final state of the updated dataset.
Describes a job.
Used in:
, , , , ,Job name.
Job configuration.
Job status.
Job statistics.
Query job completed event.
Used in:
Name of the event.
Job information.
Job configuration information. See the [Jobs](/bigquery/docs/reference/v2/jobs) API resource for more details on individual fields.
Used in:
Job configuration information.
Query job information.
Load job information.
Extract job information.
TableCopy job information.
If true, don't actually run the job. Just check that it would run.
Describes an extract job, which exports data to an external source via the export pipeline.
Used in:
Google Cloud Storage URIs where extracted data should be written.
The source table.
Describes a load job, which loads data from an external source via the import pipeline.
Used in:
URIs for the data to be imported. Only Google Cloud Storage URIs are supported.
The table schema in JSON format representation of a TableSchema.
The table where the imported data is written.
Describes when a job is allowed to create a table: `CREATE_IF_NEEDED`, `CREATE_NEVER`.
Describes how writes affect existing tables: `WRITE_TRUNCATE`, `WRITE_APPEND`, `WRITE_EMPTY`.
Describes a query job, which executes a SQL-like query.
Used in:
The SQL query to run.
The table where results are written.
Describes when a job is allowed to create a table: `CREATE_IF_NEEDED`, `CREATE_NEVER`.
Describes how writes affect existing tables: `WRITE_TRUNCATE`, `WRITE_APPEND`, `WRITE_EMPTY`.
If a table name is specified without a dataset in a query, this dataset will be added to table name.
Describes data sources outside BigQuery, if needed.
Describes a copy job, which copies an existing table to another table.
Used in:
Source tables.
Destination table.
Describes when a job is allowed to create a table: `CREATE_IF_NEEDED`, `CREATE_NEVER`.
Describes how writes affect existing tables: `WRITE_TRUNCATE`, `WRITE_APPEND`, `WRITE_EMPTY`.
Job getQueryResults request.
Used in:
Maximum number of results to return.
Zero-based row number at which to start.
Job getQueryResults response.
Used in:
Total number of results in query results.
The job that was created to run the query. It completed if `job.status.state` is `DONE`. It failed if `job.status.errorResult` is also present.
Job insert request.
Used in:
Job insert request.
Job insert response.
Used in:
Job insert response.
The fully-qualified name for a job.
Used in:
The project ID.
The job ID within the project.
Job getQueryDone response.
Used in:
The job and status information. The job completed if `job.status.state` is `DONE`.
Job query request.
Used in:
The query.
The maximum number of results.
The default dataset for tables that do not have a dataset specified.
Project that the query should be charged to.
If true, don't actually run the job. Just check that it would run.
Job query response.
Used in:
The total number of rows in the full query result set.
Information about the queried job.
Job statistics that may change after a job starts.
Used in:
Time when the job was created.
Time when the job started.
Time when the job ended.
Total bytes processed for a job.
Processed bytes, adjusted by the job's CPU usage.
The tier assigned by CPU-based billing.
Running state of a job.
Used in:
State of a job: `PENDING`, `RUNNING`, or `DONE`.
If the job did not complete successfully, this field describes why.
Describes a BigQuery table. See the [Table](/bigquery/docs/reference/v2/tables) API resource for more details on individual fields. Note: `Table.schema` has been deprecated in favor of `Table.schemaJson`. `Table.schema` may continue to be present in your logs during this transition.
Used in:
, , ,The name of the table.
User-provided metadata for the table.
A JSON representation of the table's schema.
If present, this is a virtual table defined by a SQL query.
The expiration date for the table, after which the table is deleted and the storage reclaimed. If not present, the table persists indefinitely.
The time the table was created.
The time the table was last truncated by an operation with a `writeDisposition` of `WRITE_TRUNCATE`.
Table data-list request.
Used in:
Starting row offset.
Maximum number of results to return.
Describes an external data source used in a query.
Used in:
Name of the table, used in queries.
Google Cloud Storage URIs for the data to be imported.
User-provided metadata for a table.
Used in:
A short name for the table, such as`"Analytics Data - Jan 2011"`.
A long description, perhaps several paragraphs, describing the table contents in detail.
Table insert request.
Used in:
The new table.
Table insert response.
Used in:
Final state of the inserted table.
The fully-qualified name for a table.
Used in:
, , , , ,The project ID.
The dataset ID within the project.
The table ID of the table within the dataset.
Table update request.
Used in:
The table to be updated.
Table update response.
Used in:
Final state of the updated table.
Describes a virtual table defined by a SQL query.
Used in:
SQL query defining the view.