Module enums (2.33.0)

API documentation for bigquery.enums module.

How to handle automatic insert IDs when inserting rows as a stream.

The compression type to use for exported files. The default value is NONE.

DEFLATE and SNAPPY are only supported for Avro.

Specifies whether the job is allowed to create new tables. The default value is CREATE_IF_NEEDED.

Creation, truncation and append actions occur as one atomic update upon job completion.

The data types that could be used as a target type when converting decimal values.

https://cloud.google.com/bigquery/docs/reference/rest/v2/tables#DecimalTargetType

.. versionadded:: 2.21.0

The exported file format. The default value is CSV.

Tables with nested or repeated fields cannot be exported as CSV.

Specifies determinism level for JavaScript user-defined functions (UDFs).

https://cloud.google.com/bigquery/docs/reference/rest/v2/routines#DeterminismLevel

The character encoding of the data. The default is UTF_8.

BigQuery decodes the data after the raw, binary data has been split using the values of the quote and fieldDelimiter properties.

Enum of allowed entity type names in AccessEntry

Determines which statement in the script represents the "key result".

The "key result" is used to populate the schema and query results of the script job.

https://cloud.google.com/bigquery/docs/reference/rest/v2/Job#keyresultstatementkind

Specifies a priority for the query. The default value is INTERACTIVE.

Specifies an update to the destination table schema as a side effect of a load job.

The format of the data files. The default value is CSV.

Note that the set of allowed values for loading data is different than the set used for external data sources (see ExternalSourceFormat).

Supported scalar SQL query parameter types as type objects.

Enum of allowed SQL type names in schema.SchemaField.

An Enum of scalar SQL types.

Specifies the action that occurs if destination table already exists.

The default value is WRITE_APPEND.

Each action is atomic and only occurs if BigQuery is able to complete the job successfully. Creation, truncation and append actions occur as one atomic update upon job completion.