Resource: TransferOperation
A description of the execution of a transfer.
JSON representation |
---|
{ "name": string, "projectId": string, "transferSpec": { object ( |
Fields | |
---|---|
name |
A globally unique ID assigned by the system. |
projectId |
The ID of the Google Cloud project that owns the operation. |
transferSpec |
Transfer specification. |
notificationConfig |
Notification configuration. |
loggingConfig |
Cloud Logging configuration. |
startTime |
Start time of this transfer execution. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
endTime |
End time of this transfer execution. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
status |
Status of the transfer operation. |
counters |
Information about the progress of the transfer operation. |
errorBreakdowns[] |
Summarizes errors encountered with sample error log entries. |
transferJobName |
The name of the transfer job that triggers this transfer operation. |
Status
The status of a TransferOperation.
Enums | |
---|---|
STATUS_UNSPECIFIED |
Zero is an illegal value. |
IN_PROGRESS |
In progress. |
PAUSED |
Paused. |
SUCCESS |
Completed successfully. |
FAILED |
Terminated due to an unrecoverable failure. |
ABORTED |
Aborted by the user. |
QUEUED |
Temporarily delayed by the system. No user action is required. |
SUSPENDING |
The operation is suspending and draining the ongoing work to completion. |
TransferCounters
A collection of counters that report the progress of a transfer operation.
JSON representation |
---|
{ "objectsFoundFromSource": string, "bytesFoundFromSource": string, "objectsFoundOnlyFromSink": string, "bytesFoundOnlyFromSink": string, "objectsFromSourceSkippedBySync": string, "bytesFromSourceSkippedBySync": string, "objectsCopiedToSink": string, "bytesCopiedToSink": string, "objectsDeletedFromSource": string, "bytesDeletedFromSource": string, "objectsDeletedFromSink": string, "bytesDeletedFromSink": string, "objectsFromSourceFailed": string, "bytesFromSourceFailed": string, "objectsFailedToDeleteFromSink": string, "bytesFailedToDeleteFromSink": string, "directoriesFoundFromSource": string, "directoriesFailedToListFromSource": string, "directoriesSuccessfullyListedFromSource": string, "intermediateObjectsCleanedUp": string, "intermediateObjectsFailedCleanedUp": string } |
Fields | |
---|---|
objectsFoundFromSource |
Objects found in the data source that are scheduled to be transferred, excluding any that are filtered based on object conditions or skipped due to sync. |
bytesFoundFromSource |
Bytes found in the data source that are scheduled to be transferred, excluding any that are filtered based on object conditions or skipped due to sync. |
objectsFoundOnlyFromSink |
Objects found only in the data sink that are scheduled to be deleted. |
bytesFoundOnlyFromSink |
Bytes found only in the data sink that are scheduled to be deleted. |
objectsFromSourceSkippedBySync |
Objects in the data source that are not transferred because they already exist in the data sink. |
bytesFromSourceSkippedBySync |
Bytes in the data source that are not transferred because they already exist in the data sink. |
objectsCopiedToSink |
Objects that are copied to the data sink. |
bytesCopiedToSink |
Bytes that are copied to the data sink. |
objectsDeletedFromSource |
Objects that are deleted from the data source. |
bytesDeletedFromSource |
Bytes that are deleted from the data source. |
objectsDeletedFromSink |
Objects that are deleted from the data sink. |
bytesDeletedFromSink |
Bytes that are deleted from the data sink. |
objectsFromSourceFailed |
Objects in the data source that failed to be transferred or that failed to be deleted after being transferred. |
bytesFromSourceFailed |
Bytes in the data source that failed to be transferred or that failed to be deleted after being transferred. |
objectsFailedToDeleteFromSink |
Objects that failed to be deleted from the data sink. |
bytesFailedToDeleteFromSink |
Bytes that failed to be deleted from the data sink. |
directoriesFoundFromSource |
For transfers involving PosixFilesystem only. Number of directories found while listing. For example, if the root directory of the transfer is |
directoriesFailedToListFromSource |
For transfers involving PosixFilesystem only. Number of listing failures for each directory found at the source. Potential failures when listing a directory include permission failure or block failure. If listing a directory fails, no files in the directory are transferred. |
directoriesSuccessfullyListedFromSource |
For transfers involving PosixFilesystem only. Number of successful listings for each directory found at the source. |
intermediateObjectsCleanedUp |
Number of successfully cleaned up intermediate objects. |
intermediateObjectsFailedCleanedUp |
Number of intermediate objects failed cleaned up. |
ErrorSummary
A summary of errors by error code, plus a count and sample error log entries.
JSON representation |
---|
{ "errorCode": enum ( |
Fields | |
---|---|
errorCode |
Required. |
errorCount |
Required. Count of this type of error. |
errorLogEntries[] |
Error samples. At most 5 error log entries are recorded for a given error code for a single transfer operation. |
Code
The canonical error codes for Google APIs.
Enums | |
---|---|
OK |
Not an error; returned on success. HTTP Mapping: 200 OK |
CANCELLED |
The operation was cancelled, typically by the caller. HTTP Mapping: 499 Client Closed Request |
UNKNOWN |
Unknown error. For example, this error may be returned when a HTTP Mapping: 500 Internal Server Error |
INVALID_ARGUMENT |
The client specified an invalid argument. Note that this differs from HTTP Mapping: 400 Bad Request |
DEADLINE_EXCEEDED |
The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. For example, a successful response from a server could have been delayed long enough for the deadline to expire. HTTP Mapping: 504 Gateway Timeout |
NOT_FOUND |
Some requested entity (e.g., file or directory) was not found. Note to server developers: if a request is denied for an entire class of users, such as gradual feature rollout or undocumented allowlist, HTTP Mapping: 404 Not Found |
ALREADY_EXISTS |
The entity that a client attempted to create (e.g., file or directory) already exists. HTTP Mapping: 409 Conflict |
PERMISSION_DENIED |
The caller does not have permission to execute the specified operation. HTTP Mapping: 403 Forbidden |
UNAUTHENTICATED |
The request does not have valid authentication credentials for the operation. HTTP Mapping: 401 Unauthorized |
RESOURCE_EXHAUSTED |
Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space. HTTP Mapping: 429 Too Many Requests |
FAILED_PRECONDITION |
The operation was rejected because the system is not in a state required for the operation's execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc. Service implementors can use the following guidelines to decide between HTTP Mapping: 400 Bad Request |
ABORTED |
The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort. See the guidelines above for deciding between HTTP Mapping: 409 Conflict |
OUT_OF_RANGE |
The operation was attempted past the valid range. E.g., seeking or reading past end-of-file. Unlike There is a fair bit of overlap between HTTP Mapping: 400 Bad Request |
UNIMPLEMENTED |
The operation is not implemented or is not supported/enabled in this service. HTTP Mapping: 501 Not Implemented |
INTERNAL |
Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors. HTTP Mapping: 500 Internal Server Error |
UNAVAILABLE |
The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff. Note that it is not always safe to retry non-idempotent operations. See the guidelines above for deciding between HTTP Mapping: 503 Service Unavailable |
DATA_LOSS |
Unrecoverable data loss or corruption. HTTP Mapping: 500 Internal Server Error |
ErrorLogEntry
An entry describing an error that has occurred.
JSON representation |
---|
{ "url": string, "errorDetails": [ string ] } |
Fields | |
---|---|
url |
Required. A URL that refers to the target (a data source, a data sink, or an object) with which the error is associated. |
errorDetails[] |
A list of messages that carry the error details. |
Methods |
|
---|---|
|
Cancels a transfer. |
|
Gets the latest state of a long-running operation. |
|
Lists transfer operations. |
|
Pauses a transfer operation. |
|
Resumes a transfer operation that is paused. |