Google BigQuery Storage V1 Client - Class ProtoSchema (1.5.0)

Version 1.5.0

• 2.1.0 (latest)
• 2.0.0
• 1.10.4
• 1.9.0
• 1.8.0
• 1.7.1
• 1.6.0
• 1.5.0
• 1.4.1
• 1.3.2
• 1.2.12

Reference documentation and code samples for the Google BigQuery Storage V1 Client class ProtoSchema.

ProtoSchema describes the schema of the serialized protocol buffer data rows.

Generated from protobuf message google.cloud.bigquery.storage.v1.ProtoSchema

Namespace

Google \ Cloud \ BigQuery \ Storage \ V1

Methods

__construct

Constructor.

Parameters
Name	Description
data	array Optional. Data for populating the Message object.
↳ proto_descriptor	Google\Protobuf\DescriptorProto Descriptor for input message. The provided descriptor must be self contained, such that data rows sent can be fully decoded using only the single descriptor. For data rows that are compositions of multiple independent messages, this means the descriptor may need to be transformed to only use nested types: https://developers.google.com/protocol-buffers/docs/proto#nested For additional information for how proto types and values map onto BigQuery see: https://cloud.google.com/bigquery/docs/write-api#data_type_conversions

getProtoDescriptor

Descriptor for input message. The provided descriptor must be self contained, such that data rows sent can be fully decoded using only the single descriptor. For data rows that are compositions of multiple independent messages, this means the descriptor may need to be transformed to only use nested types: https://developers.google.com/protocol-buffers/docs/proto#nested For additional information for how proto types and values map onto BigQuery see: https://cloud.google.com/bigquery/docs/write-api#data_type_conversions

Returns
Type	Description
Google\Protobuf\DescriptorProto|null

hasProtoDescriptor

clearProtoDescriptor

setProtoDescriptor

Descriptor for input message. The provided descriptor must be self contained, such that data rows sent can be fully decoded using only the single descriptor. For data rows that are compositions of multiple independent messages, this means the descriptor may need to be transformed to only use nested types: https://developers.google.com/protocol-buffers/docs/proto#nested For additional information for how proto types and values map onto BigQuery see: https://cloud.google.com/bigquery/docs/write-api#data_type_conversions

Parameter
Name	Description
var	Google\Protobuf\DescriptorProto

Returns
Type	Description
$this