Resource: Job
Transcoding job resource.
JSON representation |
---|
{ "name": string, "inputUri": string, "outputUri": string, "state": enum ( |
Fields | |
---|---|
name |
The resource name of the job. Format: |
inputUri |
Input only. Specify the |
outputUri |
Input only. Specify the |
state |
Output only. The current state of the job. |
createTime |
Output only. The time the job was created. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
startTime |
Output only. The time the transcoding started. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
endTime |
Output only. The time the transcoding finished. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
ttlAfterCompletionDays |
Job time to live value in days, which will be effective after job completion. Job should be deleted automatically after the given TTL. Enter a value between 1 and 90. The default is 30. |
labels |
The labels associated with this job. You can use these to organize and group your jobs. An object containing a list of |
error |
Output only. An error object that describes the reason for the failure. This property is always present when |
mode |
The processing mode of the job. The default is |
Union field job_config . Specify the job_config for the transcoding job. If you don't specify the job_config , the API selects templateId ; this template ID is set to preset/web-hd by default. When you use a template_id to create a job, the Job.config is populated by the JobTemplate.config .job_config can be only one of the following: |
|
templateId |
Input only. Specify the User defined JobTemplate: |
config |
The configuration for this job. |
ProcessingState
The current state of the job.
Enums | |
---|---|
PROCESSING_STATE_UNSPECIFIED |
The processing state is not specified. |
PENDING |
The job is enqueued and will be picked up for processing soon. |
RUNNING |
The job is being processed. |
SUCCEEDED |
The job has been completed successfully. |
FAILED |
The job has failed. For additional information, see failureReason and failureDetails |
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 |
ProcessingMode
The processing mode of the job.
Enums | |
---|---|
PROCESSING_MODE_UNSPECIFIED |
The job processing mode is not specified. |
PROCESSING_MODE_INTERACTIVE |
The job processing mode is interactive mode. Interactive job will either be ran or rejected if quota does not allow for it. |
PROCESSING_MODE_BATCH |
The job processing mode is batch mode. Batch mode allows queuing of jobs. |
Methods |
|
---|---|
|
Creates a job in the specified region. |
|
Deletes a job. |
|
Returns the job data. |
|
Lists jobs in the specified region. |