@@ -108,13 +108,11 @@ class TransferConfig(proto.Message):
108
108
Attributes:
109
109
name (str):
110
110
The resource name of the transfer config. Transfer config
111
- names have the form of
111
+ names have the form
112
112
``projects/{project_id}/locations/{region}/transferConfigs/{config_id}``.
113
- The name is automatically generated based on the config_id
114
- specified in CreateTransferConfigRequest along with
115
- project_id and region. If config_id is not provided, usually
116
- a uuid, even though it is not guaranteed or required, will
117
- be generated for config_id.
113
+ Where ``config_id`` is usually a uuid, even though it is not
114
+ guaranteed or required. The name is ignored when creating a
115
+ transfer config.
118
116
destination_dataset_id (str):
119
117
The BigQuery target dataset id.
120
118
display_name (str):
@@ -124,7 +122,13 @@ class TransferConfig(proto.Message):
124
122
Data source id. Cannot be changed once data
125
123
transfer is created.
126
124
params (google.protobuf.struct_pb2.Struct):
127
- Data transfer specific parameters.
125
+ Parameters specific to each data source. For
126
+ more information see the bq tab in the 'Setting
127
+ up a data transfer' section for each data
128
+ source. For example the parameters for Cloud
129
+ Storage transfers are listed here:
130
+ https://cloud.google.com/bigquery-
131
+ transfer/docs/cloud-storage-transfer#bq
128
132
schedule (str):
129
133
Data transfer schedule. If the data source does not support
130
134
a custom schedule, this should be empty. If it is empty, the
@@ -166,9 +170,11 @@ class TransferConfig(proto.Message):
166
170
Output only. Region in which BigQuery dataset
167
171
is located.
168
172
notification_pubsub_topic (str):
169
- Pub/Sub topic where notifications will be
170
- sent after transfer runs associated with this
171
- transfer config finish.
173
+ Pub/Sub topic where notifications will be sent after
174
+ transfer runs associated with this transfer config finish.
175
+
176
+ The format for specifying a pubsub topic is:
177
+ ``projects/{project}/topics/{topic}``
172
178
email_preferences (google.cloud.bigquery_datatransfer_v1.types.EmailPreferences):
173
179
Email notifications will be sent according to
174
180
these preferences to the email address of the
@@ -224,8 +230,13 @@ class TransferRun(proto.Message):
224
230
Output only. Last time the data transfer run
225
231
state was updated.
226
232
params (google.protobuf.struct_pb2.Struct):
227
- Output only. Data transfer specific
228
- parameters.
233
+ Output only. Parameters specific to each data
234
+ source. For more information see the bq tab in
235
+ the 'Setting up a data transfer' section for
236
+ each data source. For example the parameters for
237
+ Cloud Storage transfers are listed here:
238
+ https://cloud.google.com/bigquery-
239
+ transfer/docs/cloud-storage-transfer#bq
229
240
destination_dataset_id (str):
230
241
Output only. The BigQuery target dataset id.
231
242
data_source_id (str):
@@ -244,9 +255,11 @@ class TransferRun(proto.Message):
244
255
depending on the current load, so ``schedule_time`` doesn't
245
256
always match this.
246
257
notification_pubsub_topic (str):
247
- Output only. Pub/Sub topic where a
248
- notification will be sent after this transfer
249
- run finishes
258
+ Output only. Pub/Sub topic where a notification will be sent
259
+ after this transfer run finishes.
260
+
261
+ The format for specifying a pubsub topic is:
262
+ ``projects/{project}/topics/{topic}``
250
263
email_preferences (google.cloud.bigquery_datatransfer_v1.types.EmailPreferences):
251
264
Output only. Email notifications will be sent
252
265
according to these preferences to the email
0 commit comments