Class BigQueryDestination (3.9.0)

Version 3.9.0

• 3.27.1 (latest)
• 3.27.0
• 3.26.4
• 3.25.1
• 3.24.3
• 3.23.0
• 3.22.0
• 3.21.0
• 3.20.1
• 3.19.1
• 3.18.1
• 3.17.1
• 3.16.0
• 3.15.0
• 3.14.2
• 3.13.1
• 3.12.0
• 3.11.0
• 3.10.0
• 3.9.1
• 3.8.1
• 3.7.1
• 3.6.1
• 3.5.0
• 3.4.0
• 3.3.0
• 3.2.1
• 3.1.0
• 2.2.2
• 2.1.0
• 2.0.0
• 1.3.2
• 1.2.0
• 1.1.0
• 1.0.0
• 0.10.0
• 0.9.0
• 0.8.0
• 0.7.0
• 0.6.0
• 0.5.0
• 0.4.1
• 0.3.0

BigQueryDestination(mapping=None, *, ignore_unknown_fields=False, **kwargs)

A BigQuery destination.

Attributes

Name	Description
dataset	str Required. The BigQuery dataset in format "projects/projectId/datasets/datasetId", to which the analysis results should be exported. If this dataset does not exist, the export call will return an INVALID_ARGUMENT error.
table_prefix	str Required. The prefix of the BigQuery tables to which the analysis results will be written. Tables will be created based on this table_prefix if not exist: -
partition_key	google.cloud.asset_v1.types.IamPolicyAnalysisOutputConfig.BigQueryDestination.PartitionKey The partition key for BigQuery partitioned table.
write_disposition	str Optional. Specifies the action that occurs if the destination table or partition already exists. The following values are supported: - WRITE_TRUNCATE: If the table or partition already exists, BigQuery overwrites the entire table or all the partitions data. - WRITE_APPEND: If the table or partition already exists, BigQuery appends the data to the table or the latest partition. - WRITE_EMPTY: If the table already exists and contains data, an error is returned. The default value is WRITE_APPEND. Each action is atomic and only occurs if BigQuery is able to complete the job successfully. Details are at https://cloud.google.com/bigquery/docs/loading-data-local#appending_to_or_overwriting_a_table_using_a_local_file.

Inheritance

builtins.object > proto.message.Message > BigQueryDestination

Classes

PartitionKey

PartitionKey(value)

This enum determines the partition key column for the bigquery tables. Partitioning can improve query performance and reduce query cost by filtering partitions. Refer to https://cloud.google.com/bigquery/docs/partitioned-tables for details.