Resource: TransferRun
Represents a data transfer run.
JSON representation |
---|
{ "name": string, "scheduleTime": string, "runTime": string, "errorStatus": { object ( |
Fields | |
---|---|
name |
Identifier. The resource name of the transfer run. Transfer run names have the form |
scheduleTime |
Minimum time after which a transfer run can be started. |
runTime |
For batch transfer runs, specifies the date and time of the data should be ingested. |
errorStatus |
Status of the transfer run. |
startTime |
Output only. Time when transfer run was started. Parameter ignored by server for input requests. |
endTime |
Output only. Time when transfer run ended. Parameter ignored by server for input requests. |
updateTime |
Output only. Last time the data transfer run state was updated. |
params |
Output only. 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 |
dataSourceId |
Output only. Data source id. |
state |
Data transfer run state. Ignored for input requests. |
userId |
Deprecated. Unique ID of the user on whose behalf transfer is done. |
schedule |
Output only. Describes the schedule of this transfer run if it was created as part of a regular schedule. For batch transfer runs that are scheduled manually, this is empty. NOTE: the system might choose to delay the schedule depending on the current load, so |
notificationPubsubTopic |
Output only. Pub/Sub topic where a notification will be sent after this transfer run finishes. The format for specifying a pubsub topic is: |
emailPreferences |
Output only. Email notifications will be sent according to these preferences to the email address of the user who owns the transfer config this run was derived from. |
Union field destination . Data transfer destination. destination can be only one of the following: |
|
destinationDatasetId |
Output only. The BigQuery target dataset id. |
Status
The Status
type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status
message contains three pieces of data: error code, error message, and error details.
You can find out more about this error model and how to work with it in the API Design Guide.
JSON representation |
---|
{ "code": integer, "message": string, "details": [ { "@type": string, field1: ..., ... } ] } |
Fields | |
---|---|
code |
The status code, which should be an enum value of |
message |
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the |
details[] |
A list of messages that carry the error details. There is a common set of message types for APIs to use. An object containing fields of an arbitrary type. An additional field |
Methods |
|
---|---|
|
Deletes the specified transfer run. |
|
Returns information about the particular transfer run. |
|
Returns information about running and completed transfer runs. |