BigQueryConfig

Attributes

dropUnknownFields

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

Output only. An output-only field that indicates whether or not the subscription can receive messages.

table

The name of the table to which to write data, of the form {projectId}:{datasetId}.{tableId}

useTopicSchema

When true, use the topic's schema as the columns to write to in BigQuery, if it exists.

writeMetadata

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.

Companion:

object

Source:

BigQueryConfig.scala

Graph

Reset zoomHide graphShow graph

Supertypes

trait Updatable[BigQueryConfig]

trait GeneratedMessage

trait Serializable

trait Product

trait Equals

class Object

trait Matchable

class Any