Struct google_pubsub1::api::BigQueryConfig
source · pub struct BigQueryConfig {
pub drop_unknown_fields: Option<bool>,
pub service_account_email: Option<String>,
pub state: Option<String>,
pub table: Option<String>,
pub use_table_schema: Option<bool>,
pub use_topic_schema: Option<bool>,
pub write_metadata: Option<bool>,
}
Expand description
Configuration for a BigQuery subscription.
This type is not used in any activity, and only used as part of another schema.
Fields§
§drop_unknown_fields: Option<bool>
Optional. 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.
service_account_email: Option<String>
Optional. The service account to use to write to BigQuery. The subscription creator or updater that specifies this field must have iam.serviceAccounts.actAs
permission on the service account. If not specified, the Pub/Sub service agent, service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com, is used.
state: Option<String>
Output only. An output-only field that indicates whether or not the subscription can receive messages.
table: Option<String>
Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
use_table_schema: Option<bool>
Optional. When true, use the BigQuery table’s schema as the columns to write to in BigQuery. use_table_schema
and use_topic_schema
cannot be enabled at the same time.
use_topic_schema: Option<bool>
Optional. When true, use the topic’s schema as the columns to write to in BigQuery, if it exists. use_topic_schema
and use_table_schema
cannot be enabled at the same time.
write_metadata: Option<bool>
Optional. 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.
Trait Implementations§
source§impl Clone for BigQueryConfig
impl Clone for BigQueryConfig
source§fn clone(&self) -> BigQueryConfig
fn clone(&self) -> BigQueryConfig
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more