Resource: TransferConfig
Represents a data transfer configuration. A transfer configuration contains all metadata needed to perform a data transfer. For example, destinationDatasetId
specifies where data should be stored. When a new transfer configuration is created, the specified destinationDatasetId
is created when needed and shared with the appropriate data source service account.
JSON representation |
---|
{ "name": string, "displayName": string, "dataSourceId": string, "params": { object }, "schedule": string, "scheduleOptions": { object ( |
Fields | |
---|---|
name |
Identifier. The resource name of the transfer config. Transfer config names have the form either |
display |
User specified display name for the data transfer. |
data |
Data source ID. This cannot be changed once data transfer is created. The full list of available data source IDs can be returned through an API call: https://cloud.google.com/bigquery-transfer/docs/reference/datatransfer/rest/v1/projects.locations.dataSources/list |
params |
Parameters specific to each data source. For more information see the bq tab in the 'Setting up a data transfer' section for each data source. For example the parameters for Cloud Storage transfers are listed here: https://cloud.google.com/bigquery-transfer/docs/cloud-storage-transfer#bq |
schedule |
Data transfer schedule. If the data source does not support a custom schedule, this should be empty. If it is empty, the default value for the data source will be used. The specified times are in UTC. Examples of valid format: NOTE: The minimum interval time between recurring transfers depends on the data source; refer to the documentation for your data source. |
schedule |
Options customizing the data transfer schedule. |
schedule |
Options customizing different types of data transfer schedule. This field replaces "schedule" and "scheduleOptions" fields. ScheduleOptionsV2 cannot be used together with ScheduleOptions/Schedule. |
data |
The number of days to look back to automatically refresh the data. For example, if |
disabled |
Is this config disabled. When set to true, no runs will be scheduled for this transfer config. |
update |
Output only. Data transfer modification time. Ignored by server on input. |
next |
Output only. Next time when data transfer will run. |
state |
Output only. State of the most recently updated transfer run. |
user |
Deprecated. Unique ID of the user on whose behalf transfer is done. |
dataset |
Output only. Region in which BigQuery dataset is located. |
notification |
Pub/Sub topic where notifications will be sent after transfer runs associated with this transfer config finish. The format for specifying a pubsub topic is: |
email |
Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config. |
encryption |
The encryption configuration part. Currently, it is only used for the optional KMS key name. The BigQuery service account of your project must be granted permissions to use the key. Read methods will return the key name applied in effect. Write methods will apply the key if it is present, or otherwise try to apply project default keys if it is absent. |
error |
Output only. Error code with detailed information about reason of the latest config failure. |
Union field destination . The desination of the transfer config. destination can be only one of the following: |
|
destination |
The BigQuery target dataset id. |
owner |
Output only. Information about the user whose credentials are used to transfer data. Populated only for |
ScheduleOptions
Options customizing the data transfer schedule.
JSON representation |
---|
{ "disableAutoScheduling": boolean, "startTime": string, "endTime": string } |
Fields | |
---|---|
disable |
If true, automatic scheduling of data transfer runs for this configuration will be disabled. The runs can be started on ad-hoc basis using transferConfigs.startManualRuns API. When automatic scheduling is disabled, the TransferConfig.schedule field will be ignored. |
start |
Specifies time to start scheduling transfer runs. The first run will be scheduled at or after the start time according to a recurrence pattern defined in the schedule string. The start time can be changed at any moment. The time when a data transfer can be triggered manually is not limited by this option. |
end |
Defines time to stop scheduling transfer runs. A transfer run cannot be scheduled at or after the end time. The end time can be changed at any moment. The time when a data transfer can be triggered manually is not limited by this option. |
ScheduleOptionsV2
V2 options customizing different types of data transfer schedule. This field supports existing time-based and manual transfer schedule. Also supports Event-Driven transfer schedule. ScheduleOptionsV2 cannot be used together with ScheduleOptions/Schedule.
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field schedule . Data transfer schedules. schedule can be only one of the following: |
|
time |
Time based transfer schedule options. This is the default schedule option. |
manual |
Manual transfer schedule. If set, the transfer run will not be auto-scheduled by the system, unless the client invokes transferConfigs.startManualRuns. This is equivalent to disableAutoScheduling = true. |
event |
Event driven transfer schedule options. If set, the transfer will be scheduled upon events arrial. |
TimeBasedSchedule
Options customizing the time based transfer schedule. Options are migrated from the original ScheduleOptions message.
JSON representation |
---|
{ "schedule": string, "startTime": string, "endTime": string } |
Fields | |
---|---|
schedule |
Data transfer schedule. If the data source does not support a custom schedule, this should be empty. If it is empty, the default value for the data source will be used. The specified times are in UTC. Examples of valid format: NOTE: The minimum interval time between recurring transfers depends on the data source; refer to the documentation for your data source. |
start |
Specifies time to start scheduling transfer runs. The first run will be scheduled at or after the start time according to a recurrence pattern defined in the schedule string. The start time can be changed at any moment. |
end |
Defines time to stop scheduling transfer runs. A transfer run cannot be scheduled at or after the end time. The end time can be changed at any moment. |
ManualSchedule
This type has no fields.
Options customizing manual transfers schedule.
EventDrivenSchedule
Options customizing EventDriven transfers schedule.
JSON representation |
---|
{ "pubsubSubscription": string } |
Fields | |
---|---|
pubsub |
Pub/Sub subscription name used to receive events. Only Google Cloud Storage data source support this option. Format: projects/{project}/subscriptions/{subscription} |
UserInfo
Information about a user.
JSON representation |
---|
{ "email": string } |
Fields | |
---|---|
email |
E-mail address of the user. |
EncryptionConfiguration
Represents the encryption configuration for a transfer.
JSON representation |
---|
{ "kmsKeyName": string } |
Fields | |
---|---|
kms |
The name of the KMS key used for encrypting BigQuery data. |
Methods |
|
---|---|
|
Creates a new data transfer configuration. |
|
Deletes a data transfer configuration, including any associated transfer runs and logs. |
|
Returns information about a data transfer config. |
|
Returns information about all transfer configs owned by a project in the specified location. |
|
Updates a data transfer configuration. |
(deprecated) |
Creates transfer runs for a time range [start_time, end_time]. |
|
Start manual transfer runs to be executed now with schedule_time equal to current time. |