proto_docs/google/pubsub/v1/pubsub.rb in google-cloud-pubsub-v1-0.18.1 vs proto_docs/google/pubsub/v1/pubsub.rb in google-cloud-pubsub-v1-0.19.0
- old
+ new
@@ -686,12 +686,13 @@
# @return [::String]
# The name of the table to which to write data, of the form
# \\{projectId}.\\{datasetId}.\\{tableId}
# @!attribute [rw] use_topic_schema
# @return [::Boolean]
- # When true, use the topic's schema as the columns to write to in BigQuery,
- # if it exists.
+ # 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.
# @!attribute [rw] write_metadata
# @return [::Boolean]
# 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
@@ -706,9 +707,14 @@
# subscription's backlog.
# @!attribute [r] state
# @return [::Google::Cloud::PubSub::V1::BigQueryConfig::State]
# Output only. An output-only field that indicates whether or not the
# subscription can receive messages.
+ # @!attribute [rw] use_table_schema
+ # @return [::Boolean]
+ # 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.
class BigQueryConfig
include ::Google::Protobuf::MessageExts
extend ::Google::Protobuf::MessageExts::ClassMethods
# Possible states for a BigQuery subscription.