Class BigQueryConfig (2.13.2)

Version 2.13.2

• 2.27.1 (latest)
• 2.27.0
• 2.26.1
• 2.25.2
• 2.23.1
• 2.22.0
• 2.21.5
• 2.20.3
• 2.19.8
• 2.18.4
• 2.17.1
• 2.16.1
• 2.15.2
• 2.14.1
• 2.13.12
• 2.12.1
• 2.11.1
• 2.10.0
• 2.9.0
• 2.8.0
• 2.7.1
• 2.6.1
• 2.5.0
• 2.4.2
• 2.3.0
• 2.2.0
• 2.1.0
• 2.0.0
• 1.7.2
• 1.6.1
• 1.5.0
• 1.4.3
• 1.3.1
• 1.2.0
• 1.1.0
• 1.0.2
• 0.45.0
• 0.44.0
• 0.43.0

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

Configuration for a BigQuery subscription.

Attributes

Name	Description
table	str The name of the table to which to write data, of the form {projectId}:{datasetId}.{tableId}
use_topic_schema	bool When true, use the topic's schema as the columns to write to in BigQuery, if it exists.
write_metadata	bool When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
drop_unknown_fields	bool When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription's backlog.
state	google.pubsub_v1.types.BigQueryConfig.State Output only. An output-only field that indicates whether or not the subscription can receive messages.

Inheritance

builtins.object > proto.message.Message > BigQueryConfig

Classes

State

State(value)

Possible states for a BigQuery subscription.