Cloud Pub/Sub V1 API - Class Google::Cloud::PubSub::V1::CloudStorageConfig::AvroConfig (v1.1.0)

Reference documentation and code samples for the Cloud Pub/Sub V1 API class Google::Cloud::PubSub::V1::CloudStorageConfig::AvroConfig.

Configuration for writing message data in Avro format. Message payloads and metadata will be written to files as an Avro binary.

Inherits

  • Object

Extended By

  • Google::Protobuf::MessageExts::ClassMethods

Includes

  • Google::Protobuf::MessageExts

Methods

#use_topic_schema

def use_topic_schema() -> ::Boolean
Returns
  • (::Boolean) — Optional. When true, the output Cloud Storage file will be serialized using the topic schema, if it exists.

#use_topic_schema=

def use_topic_schema=(value) -> ::Boolean
Parameter
  • value (::Boolean) — Optional. When true, the output Cloud Storage file will be serialized using the topic schema, if it exists.
Returns
  • (::Boolean) — Optional. When true, the output Cloud Storage file will be serialized using the topic schema, if it exists.

#write_metadata

def write_metadata() -> ::Boolean
Returns
  • (::Boolean) — Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.

#write_metadata=

def write_metadata=(value) -> ::Boolean
Parameter
  • value (::Boolean) — Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.
Returns
  • (::Boolean) — Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.