Struct google_dataproc1::api::Job
source · pub struct Job {Show 22 fields
pub done: Option<bool>,
pub driver_control_files_uri: Option<String>,
pub driver_output_resource_uri: Option<String>,
pub driver_scheduling_config: Option<DriverSchedulingConfig>,
pub flink_job: Option<FlinkJob>,
pub hadoop_job: Option<HadoopJob>,
pub hive_job: Option<HiveJob>,
pub job_uuid: Option<String>,
pub labels: Option<HashMap<String, String>>,
pub pig_job: Option<PigJob>,
pub placement: Option<JobPlacement>,
pub presto_job: Option<PrestoJob>,
pub pyspark_job: Option<PySparkJob>,
pub reference: Option<JobReference>,
pub scheduling: Option<JobScheduling>,
pub spark_job: Option<SparkJob>,
pub spark_r_job: Option<SparkRJob>,
pub spark_sql_job: Option<SparkSqlJob>,
pub status: Option<JobStatus>,
pub status_history: Option<Vec<JobStatus>>,
pub trino_job: Option<TrinoJob>,
pub yarn_applications: Option<Vec<YarnApplication>>,
}
Expand description
A Dataproc job resource.
§Activities
This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).
- regions jobs cancel projects (response)
- regions jobs get projects (response)
- regions jobs patch projects (request|response)
- regions jobs submit projects (response)
Fields§
§done: Option<bool>
Output only. Indicates whether the job is completed. If the value is false, the job is still in progress. If true, the job is completed, and status.state field will indicate if it was successful, failed, or cancelled.
driver_control_files_uri: Option<String>
Output only. If present, the location of miscellaneous control files which can be used as part of job setup and handling. If not present, control files might be placed in the same location as driver_output_uri.
driver_output_resource_uri: Option<String>
Output only. A URI pointing to the location of the stdout of the job’s driver program.
driver_scheduling_config: Option<DriverSchedulingConfig>
Optional. Driver scheduling configuration.
flink_job: Option<FlinkJob>
Optional. Job is a Flink job.
hadoop_job: Option<HadoopJob>
Optional. Job is a Hadoop job.
hive_job: Option<HiveJob>
Optional. Job is a Hive job.
job_uuid: Option<String>
Output only. A UUID that uniquely identifies a job within the project over time. This is in contrast to a user-settable reference.job_id that might be reused over time.
labels: Option<HashMap<String, String>>
Optional. The labels to associate with this job. Label keys must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). Label values can be empty, but, if present, must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). No more than 32 labels can be associated with a job.
pig_job: Option<PigJob>
Optional. Job is a Pig job.
placement: Option<JobPlacement>
Required. Job information, including how, when, and where to run the job.
presto_job: Option<PrestoJob>
Optional. Job is a Presto job.
pyspark_job: Option<PySparkJob>
Optional. Job is a PySpark job.
reference: Option<JobReference>
Optional. The fully qualified reference to the job, which can be used to obtain the equivalent REST path of the job resource. If this property is not specified when a job is created, the server generates a job_id.
scheduling: Option<JobScheduling>
Optional. Job scheduling configuration.
spark_job: Option<SparkJob>
Optional. Job is a Spark job.
spark_r_job: Option<SparkRJob>
Optional. Job is a SparkR job.
spark_sql_job: Option<SparkSqlJob>
Optional. Job is a SparkSql job.
status: Option<JobStatus>
Output only. The job status. Additional application-specific status information might be contained in the type_job and yarn_applications fields.
status_history: Option<Vec<JobStatus>>
Output only. The previous job status.
trino_job: Option<TrinoJob>
Optional. Job is a Trino job.
yarn_applications: Option<Vec<YarnApplication>>
Output only. The collection of YARN applications spun up by this job.Beta Feature: This report is available for testing purposes only. It might be changed before final release.