GetTransferConfigResult constructor

const GetTransferConfigResult({
  1. required int dataRefreshWindowDays,
  2. required String dataSourceId,
  3. required String datasetRegion,
  4. required String destinationDatasetId,
  5. required bool disabled,
  6. required String displayName,
  7. required EmailPreferencesResponse emailPreferences,
  8. required EncryptionConfigurationResponse encryptionConfiguration,
  9. required String name,
  10. required String nextRunTime,
  11. required String notificationPubsubTopic,
  12. required UserInfoResponse ownerInfo,
  13. required Map<String, String> params,
  14. required String schedule,
  15. required ScheduleOptionsResponse scheduleOptions,
  16. required String state,
  17. required String updateTime,
  18. required String userId,
})

Creates a new GetTransferConfigResult. dataRefreshWindowDays 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. dataSourceId 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 datasetRegion Region in which BigQuery dataset is located. destinationDatasetId The BigQuery target dataset id. disabled Is this config disabled. When set to true, no runs are scheduled for a given transfer. displayName User specified display name for the data transfer. emailPreferences Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config. encryptionConfiguration 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. name The resource name of the transfer config. Transfer config names have the form either projects/{project_id}/locations/{region}/transferConfigs/{config_id} or projects/{project_id}/transferConfigs/{config_id}, where config_id is usually a UUID, even though it is not guaranteed or required. The name is ignored when creating a transfer config. nextRunTime Next time when data transfer will run. notificationPubsubTopic 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} ownerInfo 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. 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: 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. scheduleOptions Options customizing the data transfer schedule. state State of the most recently updated transfer run. updateTime Data transfer modification time. Ignored by server on input. userId Deprecated. Unique ID of the user on whose behalf transfer is done.

Implementation

const GetTransferConfigResult({
  required this.dataRefreshWindowDays,
  required this.dataSourceId,
  required this.datasetRegion,
  required this.destinationDatasetId,
  required this.disabled,
  required this.displayName,
  required this.emailPreferences,
  required this.encryptionConfiguration,
  required this.name,
  required this.nextRunTime,
  required this.notificationPubsubTopic,
  required this.ownerInfo,
  required this.params,
  required this.schedule,
  required this.scheduleOptions,
  required this.state,
  required this.updateTime,
  required this.userId,
});