BigQueryConfigArgs

data class BigQueryConfigArgs(val dropUnknownFields: Output<Boolean>? = null, val table: Output<String>? = null, val useTopicSchema: Output<Boolean>? = null, val writeMetadata: Output<Boolean>? = null) : ConvertibleToJava<BigQueryConfigArgs>

Configuration for a BigQuery subscription.

Constructors

Link copied to clipboard
fun BigQueryConfigArgs(dropUnknownFields: Output<Boolean>? = null, table: Output<String>? = null, useTopicSchema: Output<Boolean>? = null, writeMetadata: Output<Boolean>? = null)

Functions

Link copied to clipboard
open override fun toJava(): BigQueryConfigArgs

Properties

Link copied to clipboard
val dropUnknownFields: Output<Boolean>? = null

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.

Link copied to clipboard
val table: Output<String>? = null

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

Link copied to clipboard
val useTopicSchema: Output<Boolean>? = null

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

Link copied to clipboard
val writeMetadata: Output<Boolean>? = null

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.