com.google.cloud.bigquery.datatransfer.v1.datasource

Data source definition.

The BigQuery project id for which data source definition is associated. Must be in the form: projects/{project_id}/locations/{location_id}

Data source metadata.

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.

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

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.

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.

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

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;

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.

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.

The field will contain name of the resource requested, for example: projects/{project_id}/locations/{location_id}/dataSourceDefinitions/{data_source_id}

Name of the resource in the form: "projects/{project_id}/locations/{location_id}/transferConfigs/{config_id}/runs/{run_id}"

The field will contain name of the resource requested.

The description of a destination table. This can be several sentences or paragraphs describing the table contents in detail.

Table where results should be written.

SQL query to run. When empty, API checks that there is only one table_def specified and loads this table. Only Standard SQL queries are accepted. Legacy SQL is not allowed.

When used WITHOUT the "sql" parameter, describes the schema of the destination table. When used WITH the "sql" parameter, describes tables with data stored outside of BigQuery.

Inline code for User-defined function resources. Ignored when "sql" parameter is empty.

Specifies the action if the destination table already exists.

Page size. The default page size is the maximum value of 1000 results.

Pagination token, which can be used to request a specific page of ListDataSourceDefinitionsRequest list results. For multiple-page results, ListDataSourceDefinitionsResponse outputs a next_page token, which can be used as the page_token value to request the next page of the list results.

The BigQuery project id for which data sources should be returned. Must be in the form: projects/{project_id}/locations/{location_id}

List of supported data source definitions.

Output only. The next-pagination token. For multiple-page list results, this token can be used as the ListDataSourceDefinitionsRequest.page_token to request the next page of the list results.

Name of the resource in the form: "projects/{project_id}/locations/{location_id}/transferConfigs/{config_id}/runs/{run_id}"

Messages to append.

Import jobs which should be started and monitored.

The number of BQ Jobs that can run in parallel.

Name of the resource in the form: "projects/{project_id}/locations/{location_id}/transferConfigs/{config_id}/runs/{run_id}"

User credentials which should be used to start/monitor BigQuery jobs. If not specified, then jobs are started using data source service account credentials. This may be OAuth token or JWT token.

Data source definition.

Update field mask.

Run name must be set and correspond to an already existing run. Only state, error_status, and data_version fields will be updated. All other fields will be ignored.

Required list of fields to be updated in this request.