Get Transfer Config Result
Constructors
Properties
The number of days to look back to automatically refresh the data. For example, if data_refresh_window_days = 10
, then every day BigQuery reingests data for today-10, today-1, rather than ingesting data for just today-1. Only valid if the data source supports the feature. Set the value to 0 to use the default value.
Region in which BigQuery dataset is located.
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
The BigQuery target dataset id.
User specified display name for the data transfer.
Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config.
Next time when data transfer will run.
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: projects/{project}/topics/{topic}
Information about the user whose credentials are used to transfer data. Populated only for transferConfigs.get
requests. In case the user information is not available, this field will not be populated.
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
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: 1st,3rd monday of month 15:30
, every wed,fri of jan,jun 13:15
, and first sunday of quarter 00:00
. See more explanation about the format here: https://cloud.google.com/appengine/docs/flexible/python/scheduling-jobs-with-cron-yaml#the_schedule_format NOTE: The minimum interval time between recurring transfers depends on the data source; refer to the documentation for your data source.
Options customizing the data transfer schedule.
Data transfer modification time. Ignored by server on input.