Class DataSourceDefinition.Builder (2.0.27)

public static final class DataSourceDefinition.Builder extends GeneratedMessageV3.Builder<DataSourceDefinition.Builder> implements DataSourceDefinitionOrBuilder

Represents the data source definition.

Protobuf type google.cloud.bigquery.datatransfer.v1.DataSourceDefinition

Methods

addAllSupportedLocationIds(Iterable<String> values)

public DataSourceDefinition.Builder addAllSupportedLocationIds(Iterable<String> values)

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Parameter
NameDescription
valuesIterable<String>
Returns
TypeDescription
DataSourceDefinition.Builder

addRepeatedField(Descriptors.FieldDescriptor field, Object value)

public DataSourceDefinition.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Parameters
NameDescription
fieldFieldDescriptor
valueObject
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

addSupportedLocationIds(String value)

public DataSourceDefinition.Builder addSupportedLocationIds(String value)

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Parameter
NameDescription
valueString
Returns
TypeDescription
DataSourceDefinition.Builder

addSupportedLocationIdsBytes(ByteString value)

public DataSourceDefinition.Builder addSupportedLocationIdsBytes(ByteString value)

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Parameter
NameDescription
valueByteString
Returns
TypeDescription
DataSourceDefinition.Builder

build()

public DataSourceDefinition build()
Returns
TypeDescription
DataSourceDefinition

buildPartial()

public DataSourceDefinition buildPartial()
Returns
TypeDescription
DataSourceDefinition

clear()

public DataSourceDefinition.Builder clear()
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

clearDataSource()

public DataSourceDefinition.Builder clearDataSource()

Data source metadata.

.google.cloud.bigquery.datatransfer.v1.DataSource data_source = 1;

Returns
TypeDescription
DataSourceDefinition.Builder

clearDisabled()

public DataSourceDefinition.Builder clearDisabled()

Is data source disabled? If true, data_source is not visible. API will also stop returning any data transfer configs and/or runs associated with the data source. This setting has higher priority than whitelisted_project_ids.

bool disabled = 5;

Returns
TypeDescription
DataSourceDefinition.Builder

clearField(Descriptors.FieldDescriptor field)

public DataSourceDefinition.Builder clearField(Descriptors.FieldDescriptor field)
Parameter
NameDescription
fieldFieldDescriptor
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

clearName()

public DataSourceDefinition.Builder clearName()

The resource name of the data source definition. Data source definition names have the form projects/{project_id}/locations/{location}/dataSourceDefinitions/{data_source_id}.

string name = 21;

Returns
TypeDescription
DataSourceDefinition.Builder

clearOneof(Descriptors.OneofDescriptor oneof)

public DataSourceDefinition.Builder clearOneof(Descriptors.OneofDescriptor oneof)
Parameter
NameDescription
oneofOneofDescriptor
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

clearRunTimeOffset()

public DataSourceDefinition.Builder clearRunTimeOffset()

Duration which should be added to schedule_time to calculate run_time when job is scheduled. Only applicable for automatically scheduled transfer runs. Used to start a run early on a data source that supports continuous data refresh to compensate for unknown timezone offsets. Use a negative number to start a run late for data sources not supporting continuous data refresh.

.google.protobuf.Duration run_time_offset = 16;

Returns
TypeDescription
DataSourceDefinition.Builder

clearServiceAccount()

public DataSourceDefinition.Builder clearServiceAccount()

When service account is specified, BigQuery will share created dataset with the given service account. Also, this service account will be eligible to perform status updates and message logging for data transfer runs for the corresponding data_source_id.

string service_account = 2;

Returns
TypeDescription
DataSourceDefinition.Builder

clearSupportEmail()

public DataSourceDefinition.Builder clearSupportEmail()

Support e-mail address of the OAuth client's Brand, which contains the consent screen data.

string support_email = 22;

Returns
TypeDescription
DataSourceDefinition.Builder

clearSupportedLocationIds()

public DataSourceDefinition.Builder clearSupportedLocationIds()

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Returns
TypeDescription
DataSourceDefinition.Builder

clearTransferConfigPubsubTopic()

public DataSourceDefinition.Builder clearTransferConfigPubsubTopic()

The Pub/Sub topic to use for broadcasting a message for transfer config. If empty, a message will not be broadcasted. Both this topic and transfer_run_pubsub_topic are auto-generated if none of them is provided when creating the definition. It is recommended to provide transfer_config_pubsub_topic if a user-owned transfer_run_pubsub_topic is provided. Otherwise, it will be set to empty. If "{location}" is found in the value, then that means, data source wants to handle message separately for datasets in different regions. We will replace {location} with the actual dataset location, as the actual topic name. For example, projects/connector/topics/scheduler-{location} could become projects/connector/topics/scheduler-us. If "{location}" is not found, then we will use the input value as topic name.

string transfer_config_pubsub_topic = 12;

Returns
TypeDescription
DataSourceDefinition.Builder

clearTransferRunPubsubTopic()

public DataSourceDefinition.Builder clearTransferRunPubsubTopic()

The Pub/Sub topic to be used for broadcasting a message when a transfer run is created. Both this topic and transfer_config_pubsub_topic can be set to a custom topic. By default, both topics are auto-generated if none of them is provided when creating the definition. However, if one topic is manually set, the other topic has to be manually set as well. The only difference is that transfer_run_pubsub_topic must be a non-empty Pub/Sub topic, but transfer_config_pubsub_topic can be set to empty. The comments about "{location}" for transfer_config_pubsub_topic apply here too.

string transfer_run_pubsub_topic = 13;

Returns
TypeDescription
DataSourceDefinition.Builder

clone()

public DataSourceDefinition.Builder clone()
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

getDataSource()

public DataSource getDataSource()

Data source metadata.

.google.cloud.bigquery.datatransfer.v1.DataSource data_source = 1;

Returns
TypeDescription
DataSource

getDataSourceBuilder()

public DataSource.Builder getDataSourceBuilder()

Data source metadata.

.google.cloud.bigquery.datatransfer.v1.DataSource data_source = 1;

Returns
TypeDescription
DataSource.Builder

getDataSourceOrBuilder()

public DataSourceOrBuilder getDataSourceOrBuilder()

Data source metadata.

.google.cloud.bigquery.datatransfer.v1.DataSource data_source = 1;

Returns
TypeDescription
DataSourceOrBuilder

getDefaultInstanceForType()

public DataSourceDefinition getDefaultInstanceForType()
Returns
TypeDescription
DataSourceDefinition

getDescriptor()

public static final Descriptors.Descriptor getDescriptor()
Returns
TypeDescription
Descriptor

getDescriptorForType()

public Descriptors.Descriptor getDescriptorForType()
Returns
TypeDescription
Descriptor
Overrides

getDisabled()

public boolean getDisabled()

Is data source disabled? If true, data_source is not visible. API will also stop returning any data transfer configs and/or runs associated with the data source. This setting has higher priority than whitelisted_project_ids.

bool disabled = 5;

Returns
TypeDescription
boolean

getName()

public String getName()

The resource name of the data source definition. Data source definition names have the form projects/{project_id}/locations/{location}/dataSourceDefinitions/{data_source_id}.

string name = 21;

Returns
TypeDescription
String

getNameBytes()

public ByteString getNameBytes()

The resource name of the data source definition. Data source definition names have the form projects/{project_id}/locations/{location}/dataSourceDefinitions/{data_source_id}.

string name = 21;

Returns
TypeDescription
ByteString

getRunTimeOffset()

public Duration getRunTimeOffset()

Duration which should be added to schedule_time to calculate run_time when job is scheduled. Only applicable for automatically scheduled transfer runs. Used to start a run early on a data source that supports continuous data refresh to compensate for unknown timezone offsets. Use a negative number to start a run late for data sources not supporting continuous data refresh.

.google.protobuf.Duration run_time_offset = 16;

Returns
TypeDescription
Duration

getRunTimeOffsetBuilder()

public Duration.Builder getRunTimeOffsetBuilder()

Duration which should be added to schedule_time to calculate run_time when job is scheduled. Only applicable for automatically scheduled transfer runs. Used to start a run early on a data source that supports continuous data refresh to compensate for unknown timezone offsets. Use a negative number to start a run late for data sources not supporting continuous data refresh.

.google.protobuf.Duration run_time_offset = 16;

Returns
TypeDescription
Builder

getRunTimeOffsetOrBuilder()

public DurationOrBuilder getRunTimeOffsetOrBuilder()

Duration which should be added to schedule_time to calculate run_time when job is scheduled. Only applicable for automatically scheduled transfer runs. Used to start a run early on a data source that supports continuous data refresh to compensate for unknown timezone offsets. Use a negative number to start a run late for data sources not supporting continuous data refresh.

.google.protobuf.Duration run_time_offset = 16;

Returns
TypeDescription
DurationOrBuilder

getServiceAccount()

public String getServiceAccount()

When service account is specified, BigQuery will share created dataset with the given service account. Also, this service account will be eligible to perform status updates and message logging for data transfer runs for the corresponding data_source_id.

string service_account = 2;

Returns
TypeDescription
String

getServiceAccountBytes()

public ByteString getServiceAccountBytes()

When service account is specified, BigQuery will share created dataset with the given service account. Also, this service account will be eligible to perform status updates and message logging for data transfer runs for the corresponding data_source_id.

string service_account = 2;

Returns
TypeDescription
ByteString

getSupportEmail()

public String getSupportEmail()

Support e-mail address of the OAuth client's Brand, which contains the consent screen data.

string support_email = 22;

Returns
TypeDescription
String

getSupportEmailBytes()

public ByteString getSupportEmailBytes()

Support e-mail address of the OAuth client's Brand, which contains the consent screen data.

string support_email = 22;

Returns
TypeDescription
ByteString

getSupportedLocationIds(int index)

public String getSupportedLocationIds(int index)

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Parameter
NameDescription
indexint
Returns
TypeDescription
String

getSupportedLocationIdsBytes(int index)

public ByteString getSupportedLocationIdsBytes(int index)

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Parameter
NameDescription
indexint
Returns
TypeDescription
ByteString

getSupportedLocationIdsCount()

public int getSupportedLocationIdsCount()

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Returns
TypeDescription
int

getSupportedLocationIdsList()

public ProtocolStringList getSupportedLocationIdsList()

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Returns
TypeDescription
ProtocolStringList

getTransferConfigPubsubTopic()

public String getTransferConfigPubsubTopic()

The Pub/Sub topic to use for broadcasting a message for transfer config. If empty, a message will not be broadcasted. Both this topic and transfer_run_pubsub_topic are auto-generated if none of them is provided when creating the definition. It is recommended to provide transfer_config_pubsub_topic if a user-owned transfer_run_pubsub_topic is provided. Otherwise, it will be set to empty. If "{location}" is found in the value, then that means, data source wants to handle message separately for datasets in different regions. We will replace {location} with the actual dataset location, as the actual topic name. For example, projects/connector/topics/scheduler-{location} could become projects/connector/topics/scheduler-us. If "{location}" is not found, then we will use the input value as topic name.

string transfer_config_pubsub_topic = 12;

Returns
TypeDescription
String

getTransferConfigPubsubTopicBytes()

public ByteString getTransferConfigPubsubTopicBytes()

The Pub/Sub topic to use for broadcasting a message for transfer config. If empty, a message will not be broadcasted. Both this topic and transfer_run_pubsub_topic are auto-generated if none of them is provided when creating the definition. It is recommended to provide transfer_config_pubsub_topic if a user-owned transfer_run_pubsub_topic is provided. Otherwise, it will be set to empty. If "{location}" is found in the value, then that means, data source wants to handle message separately for datasets in different regions. We will replace {location} with the actual dataset location, as the actual topic name. For example, projects/connector/topics/scheduler-{location} could become projects/connector/topics/scheduler-us. If "{location}" is not found, then we will use the input value as topic name.

string transfer_config_pubsub_topic = 12;

Returns
TypeDescription
ByteString

getTransferRunPubsubTopic()

public String getTransferRunPubsubTopic()

The Pub/Sub topic to be used for broadcasting a message when a transfer run is created. Both this topic and transfer_config_pubsub_topic can be set to a custom topic. By default, both topics are auto-generated if none of them is provided when creating the definition. However, if one topic is manually set, the other topic has to be manually set as well. The only difference is that transfer_run_pubsub_topic must be a non-empty Pub/Sub topic, but transfer_config_pubsub_topic can be set to empty. The comments about "{location}" for transfer_config_pubsub_topic apply here too.

string transfer_run_pubsub_topic = 13;

Returns
TypeDescription
String

getTransferRunPubsubTopicBytes()

public ByteString getTransferRunPubsubTopicBytes()

The Pub/Sub topic to be used for broadcasting a message when a transfer run is created. Both this topic and transfer_config_pubsub_topic can be set to a custom topic. By default, both topics are auto-generated if none of them is provided when creating the definition. However, if one topic is manually set, the other topic has to be manually set as well. The only difference is that transfer_run_pubsub_topic must be a non-empty Pub/Sub topic, but transfer_config_pubsub_topic can be set to empty. The comments about "{location}" for transfer_config_pubsub_topic apply here too.

string transfer_run_pubsub_topic = 13;

Returns
TypeDescription
ByteString

hasDataSource()

public boolean hasDataSource()

Data source metadata.

.google.cloud.bigquery.datatransfer.v1.DataSource data_source = 1;

Returns
TypeDescription
boolean

hasRunTimeOffset()

public boolean hasRunTimeOffset()

Duration which should be added to schedule_time to calculate run_time when job is scheduled. Only applicable for automatically scheduled transfer runs. Used to start a run early on a data source that supports continuous data refresh to compensate for unknown timezone offsets. Use a negative number to start a run late for data sources not supporting continuous data refresh.

.google.protobuf.Duration run_time_offset = 16;

Returns
TypeDescription
boolean

internalGetFieldAccessorTable()

protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Returns
TypeDescription
FieldAccessorTable
Overrides

isInitialized()

public final boolean isInitialized()
Returns
TypeDescription
boolean
Overrides

mergeDataSource(DataSource value)

public DataSourceDefinition.Builder mergeDataSource(DataSource value)

Data source metadata.

.google.cloud.bigquery.datatransfer.v1.DataSource data_source = 1;

Parameter
NameDescription
valueDataSource
Returns
TypeDescription
DataSourceDefinition.Builder

mergeFrom(DataSourceDefinition other)

public DataSourceDefinition.Builder mergeFrom(DataSourceDefinition other)
Parameter
NameDescription
otherDataSourceDefinition
Returns
TypeDescription
DataSourceDefinition.Builder

mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)

public DataSourceDefinition.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Parameters
NameDescription
inputCodedInputStream
extensionRegistryExtensionRegistryLite
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides Exceptions
TypeDescription
IOException

mergeFrom(Message other)

public DataSourceDefinition.Builder mergeFrom(Message other)
Parameter
NameDescription
otherMessage
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

mergeRunTimeOffset(Duration value)

public DataSourceDefinition.Builder mergeRunTimeOffset(Duration value)

Duration which should be added to schedule_time to calculate run_time when job is scheduled. Only applicable for automatically scheduled transfer runs. Used to start a run early on a data source that supports continuous data refresh to compensate for unknown timezone offsets. Use a negative number to start a run late for data sources not supporting continuous data refresh.

.google.protobuf.Duration run_time_offset = 16;

Parameter
NameDescription
valueDuration
Returns
TypeDescription
DataSourceDefinition.Builder

mergeUnknownFields(UnknownFieldSet unknownFields)

public final DataSourceDefinition.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Parameter
NameDescription
unknownFieldsUnknownFieldSet
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

setDataSource(DataSource value)

public DataSourceDefinition.Builder setDataSource(DataSource value)

Data source metadata.

.google.cloud.bigquery.datatransfer.v1.DataSource data_source = 1;

Parameter
NameDescription
valueDataSource
Returns
TypeDescription
DataSourceDefinition.Builder

setDataSource(DataSource.Builder builderForValue)

public DataSourceDefinition.Builder setDataSource(DataSource.Builder builderForValue)

Data source metadata.

.google.cloud.bigquery.datatransfer.v1.DataSource data_source = 1;

Parameter
NameDescription
builderForValueDataSource.Builder
Returns
TypeDescription
DataSourceDefinition.Builder

setDisabled(boolean value)

public DataSourceDefinition.Builder setDisabled(boolean value)

Is data source disabled? If true, data_source is not visible. API will also stop returning any data transfer configs and/or runs associated with the data source. This setting has higher priority than whitelisted_project_ids.

bool disabled = 5;

Parameter
NameDescription
valueboolean
Returns
TypeDescription
DataSourceDefinition.Builder

setField(Descriptors.FieldDescriptor field, Object value)

public DataSourceDefinition.Builder setField(Descriptors.FieldDescriptor field, Object value)
Parameters
NameDescription
fieldFieldDescriptor
valueObject
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

setName(String value)

public DataSourceDefinition.Builder setName(String value)

The resource name of the data source definition. Data source definition names have the form projects/{project_id}/locations/{location}/dataSourceDefinitions/{data_source_id}.

string name = 21;

Parameter
NameDescription
valueString
Returns
TypeDescription
DataSourceDefinition.Builder

setNameBytes(ByteString value)

public DataSourceDefinition.Builder setNameBytes(ByteString value)

The resource name of the data source definition. Data source definition names have the form projects/{project_id}/locations/{location}/dataSourceDefinitions/{data_source_id}.

string name = 21;

Parameter
NameDescription
valueByteString
Returns
TypeDescription
DataSourceDefinition.Builder

setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)

public DataSourceDefinition.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Parameters
NameDescription
fieldFieldDescriptor
indexint
valueObject
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides

setRunTimeOffset(Duration value)

public DataSourceDefinition.Builder setRunTimeOffset(Duration value)

Duration which should be added to schedule_time to calculate run_time when job is scheduled. Only applicable for automatically scheduled transfer runs. Used to start a run early on a data source that supports continuous data refresh to compensate for unknown timezone offsets. Use a negative number to start a run late for data sources not supporting continuous data refresh.

.google.protobuf.Duration run_time_offset = 16;

Parameter
NameDescription
valueDuration
Returns
TypeDescription
DataSourceDefinition.Builder

setRunTimeOffset(Duration.Builder builderForValue)

public DataSourceDefinition.Builder setRunTimeOffset(Duration.Builder builderForValue)

Duration which should be added to schedule_time to calculate run_time when job is scheduled. Only applicable for automatically scheduled transfer runs. Used to start a run early on a data source that supports continuous data refresh to compensate for unknown timezone offsets. Use a negative number to start a run late for data sources not supporting continuous data refresh.

.google.protobuf.Duration run_time_offset = 16;

Parameter
NameDescription
builderForValueBuilder
Returns
TypeDescription
DataSourceDefinition.Builder

setServiceAccount(String value)

public DataSourceDefinition.Builder setServiceAccount(String value)

When service account is specified, BigQuery will share created dataset with the given service account. Also, this service account will be eligible to perform status updates and message logging for data transfer runs for the corresponding data_source_id.

string service_account = 2;

Parameter
NameDescription
valueString
Returns
TypeDescription
DataSourceDefinition.Builder

setServiceAccountBytes(ByteString value)

public DataSourceDefinition.Builder setServiceAccountBytes(ByteString value)

When service account is specified, BigQuery will share created dataset with the given service account. Also, this service account will be eligible to perform status updates and message logging for data transfer runs for the corresponding data_source_id.

string service_account = 2;

Parameter
NameDescription
valueByteString
Returns
TypeDescription
DataSourceDefinition.Builder

setSupportEmail(String value)

public DataSourceDefinition.Builder setSupportEmail(String value)

Support e-mail address of the OAuth client's Brand, which contains the consent screen data.

string support_email = 22;

Parameter
NameDescription
valueString
Returns
TypeDescription
DataSourceDefinition.Builder

setSupportEmailBytes(ByteString value)

public DataSourceDefinition.Builder setSupportEmailBytes(ByteString value)

Support e-mail address of the OAuth client's Brand, which contains the consent screen data.

string support_email = 22;

Parameter
NameDescription
valueByteString
Returns
TypeDescription
DataSourceDefinition.Builder

setSupportedLocationIds(int index, String value)

public DataSourceDefinition.Builder setSupportedLocationIds(int index, String value)

Supported location_ids used for deciding in which locations Pub/Sub topics need to be created. If custom Pub/Sub topics are used and they contains '{location}', the location_ids will be used for validating the topics by replacing the '{location}' with the individual location in the list. The valid values are the "location_id" field of the response of GET https://bigquerydatatransfer.googleapis.com/v1/{name=projects/*}/locations In addition, if the data source needs to support all available regions, supported_location_ids can be set to "global" (a single string element). When "global" is specified: 1) the data source implementation is supposed to stage the data in proper region of the destination dataset; 2) Data source developer should be aware of the implications (e.g., network traffic latency, potential charge associated with cross-region traffic, etc.) of supporting the "global" region;

repeated string supported_location_ids = 23;

Parameters
NameDescription
indexint
valueString
Returns
TypeDescription
DataSourceDefinition.Builder

setTransferConfigPubsubTopic(String value)

public DataSourceDefinition.Builder setTransferConfigPubsubTopic(String value)

The Pub/Sub topic to use for broadcasting a message for transfer config. If empty, a message will not be broadcasted. Both this topic and transfer_run_pubsub_topic are auto-generated if none of them is provided when creating the definition. It is recommended to provide transfer_config_pubsub_topic if a user-owned transfer_run_pubsub_topic is provided. Otherwise, it will be set to empty. If "{location}" is found in the value, then that means, data source wants to handle message separately for datasets in different regions. We will replace {location} with the actual dataset location, as the actual topic name. For example, projects/connector/topics/scheduler-{location} could become projects/connector/topics/scheduler-us. If "{location}" is not found, then we will use the input value as topic name.

string transfer_config_pubsub_topic = 12;

Parameter
NameDescription
valueString
Returns
TypeDescription
DataSourceDefinition.Builder

setTransferConfigPubsubTopicBytes(ByteString value)

public DataSourceDefinition.Builder setTransferConfigPubsubTopicBytes(ByteString value)

The Pub/Sub topic to use for broadcasting a message for transfer config. If empty, a message will not be broadcasted. Both this topic and transfer_run_pubsub_topic are auto-generated if none of them is provided when creating the definition. It is recommended to provide transfer_config_pubsub_topic if a user-owned transfer_run_pubsub_topic is provided. Otherwise, it will be set to empty. If "{location}" is found in the value, then that means, data source wants to handle message separately for datasets in different regions. We will replace {location} with the actual dataset location, as the actual topic name. For example, projects/connector/topics/scheduler-{location} could become projects/connector/topics/scheduler-us. If "{location}" is not found, then we will use the input value as topic name.

string transfer_config_pubsub_topic = 12;

Parameter
NameDescription
valueByteString
Returns
TypeDescription
DataSourceDefinition.Builder

setTransferRunPubsubTopic(String value)

public DataSourceDefinition.Builder setTransferRunPubsubTopic(String value)

The Pub/Sub topic to be used for broadcasting a message when a transfer run is created. Both this topic and transfer_config_pubsub_topic can be set to a custom topic. By default, both topics are auto-generated if none of them is provided when creating the definition. However, if one topic is manually set, the other topic has to be manually set as well. The only difference is that transfer_run_pubsub_topic must be a non-empty Pub/Sub topic, but transfer_config_pubsub_topic can be set to empty. The comments about "{location}" for transfer_config_pubsub_topic apply here too.

string transfer_run_pubsub_topic = 13;

Parameter
NameDescription
valueString
Returns
TypeDescription
DataSourceDefinition.Builder

setTransferRunPubsubTopicBytes(ByteString value)

public DataSourceDefinition.Builder setTransferRunPubsubTopicBytes(ByteString value)

The Pub/Sub topic to be used for broadcasting a message when a transfer run is created. Both this topic and transfer_config_pubsub_topic can be set to a custom topic. By default, both topics are auto-generated if none of them is provided when creating the definition. However, if one topic is manually set, the other topic has to be manually set as well. The only difference is that transfer_run_pubsub_topic must be a non-empty Pub/Sub topic, but transfer_config_pubsub_topic can be set to empty. The comments about "{location}" for transfer_config_pubsub_topic apply here too.

string transfer_run_pubsub_topic = 13;

Parameter
NameDescription
valueByteString
Returns
TypeDescription
DataSourceDefinition.Builder

setUnknownFields(UnknownFieldSet unknownFields)

public final DataSourceDefinition.Builder setUnknownFields(UnknownFieldSet unknownFields)
Parameter
NameDescription
unknownFieldsUnknownFieldSet
Returns
TypeDescription
DataSourceDefinition.Builder
Overrides