Get Job Result
Constructors
Properties
If present, the location of miscellaneous control files which may be used as part of job setup and handling. If not present, control files may be placed in the same location as driver_output_uri.
A URI pointing to the location of the stdout of the job's driver program.
Optional. Job is a Hadoop job.
Optional. Job is a Hive job.
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 may 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.
Optional. Job is a Pig job.
Job information, including how, when, and where to run the job.
Optional. Job is a Presto job.
Optional. Job is a PySpark job.
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.
Optional. Job scheduling configuration.
Optional. Job is a Spark job.
Optional. Job is a SparkR job.
Optional. Job is a SparkSql job.
The job status. Additional application-specific status information may be contained in the type_job and yarn_applications fields.
The previous job status.
The email address of the user submitting the job. For jobs submitted on the cluster, the address is username@hostname.
The collection of YARN applications spun up by this job.Beta Feature: This report is available for testing purposes only. It may be changed before final release.