Get desktop application:
View/edit binary Protocol Buffers messages
The ClusterControllerService provides methods to manage clusters of Google Compute Engine instances.
Creates a cluster in a project.
A request to create a cluster.
Required. The ID of the Google Cloud Platform project that the cluster belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The cluster to create.
Deletes a cluster in a project.
A request to delete a cluster.
Required. The ID of the Google Cloud Platform project that the cluster belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The cluster name.
Gets cluster diagnostic information. After the operation completes, the Operation.response field contains `DiagnoseClusterOutputLocation`.
A request to collect cluster diagnostic information.
Required. The ID of the Google Cloud Platform project that the cluster belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The cluster name.
Gets the resource representation for a cluster in a project.
Request to get the resource representation for a cluster in a project.
Required. The ID of the Google Cloud Platform project that the cluster belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The cluster name.
Lists all regions/{region}/clusters in a project.
A request to list the clusters in a project.
Required. The ID of the Google Cloud Platform project that the cluster belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Optional. A filter constraining the clusters to list. Filters are case-sensitive and have the following syntax: field = value [AND [field = value]] ... where **field** is one of `status.state`, `clusterName`, or `labels.[KEY]`, and `[KEY]` is a label key. **value** can be `*` to match all values. `status.state` can be one of the following: `ACTIVE`, `INACTIVE`, `CREATING`, `RUNNING`, `ERROR`, `DELETING`, or `UPDATING`. `ACTIVE` contains the `CREATING`, `UPDATING`, and `RUNNING` states. `INACTIVE` contains the `DELETING` and `ERROR` states. `clusterName` is the name of the cluster provided at creation time. Only the logical `AND` operator is supported; space-separated items are treated as having an implicit `AND` operator. Example filter: status.state = ACTIVE AND clusterName = mycluster AND labels.env = staging AND labels.starred = *
Optional. The standard List page size.
Optional. The standard List page token.
The list of all clusters in a project.
Output-only. The clusters in the project.
Output-only. This token is included in the response if there are more results to fetch. To fetch additional results, provide this value as the `page_token` in a subsequent `ListClustersRequest`.
Updates a cluster in a project.
A request to update a cluster.
Required. The ID of the Google Cloud Platform project the cluster belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The cluster name.
Required. The changes to the cluster.
Required. Specifies the path, relative to `Cluster`, of the field to update. For example, to change the number of workers in a cluster to 5, the `update_mask` parameter would be specified as `config.worker_config.num_instances`, and the `PATCH` request body would specify the new value, as follows: { "config":{ "workerConfig":{ "numInstances":"5" } } } Similarly, to change the number of preemptible workers in a cluster to 5, the `update_mask` parameter would be `config.secondary_worker_config.num_instances`, and the `PATCH` request body would be set as follows: { "config":{ "secondaryWorkerConfig":{ "numInstances":"5" } } } <strong>Note:</strong> Currently, only the following fields can be updated: <table> <tbody> <tr> <td><strong>Mask</strong></td> <td><strong>Purpose</strong></td> </tr> <tr> <td><strong><em>labels</em></strong></td> <td>Update labels</td> </tr> <tr> <td><strong><em>config.worker_config.num_instances</em></strong></td> <td>Resize primary worker group</td> </tr> <tr> <td><strong><em>config.secondary_worker_config.num_instances</em></strong></td> <td>Resize secondary worker group</td> </tr> </tbody> </table>
The JobController provides methods to manage jobs.
Starts a job cancellation request. To access the job resource after cancellation, call [regions/{region}/jobs.list](/dataproc/docs/reference/rest/v1/projects.regions.jobs/list) or [regions/{region}/jobs.get](/dataproc/docs/reference/rest/v1/projects.regions.jobs/get).
A request to cancel a job.
Required. The ID of the Google Cloud Platform project that the job belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The job ID.
Deletes the job from the project. If the job is active, the delete fails, and the response returns `FAILED_PRECONDITION`.
A request to delete a job.
Required. The ID of the Google Cloud Platform project that the job belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The job ID.
Gets the resource representation for a job in a project.
A request to get the resource representation for a job in a project.
Required. The ID of the Google Cloud Platform project that the job belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The job ID.
Lists regions/{region}/jobs in a project.
A request to list jobs in a project.
Required. The ID of the Google Cloud Platform project that the job belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Optional. The number of results to return in each response.
Optional. The page token, returned by a previous call, to request the next page of results.
Optional. If set, the returned jobs list includes only jobs that were submitted to the named cluster.
Optional. Specifies enumerated categories of jobs to list. (default = match ALL jobs). If `filter` is provided, `jobStateMatcher` will be ignored.
Optional. A filter constraining the jobs to list. Filters are case-sensitive and have the following syntax: [field = value] AND [field [= value]] ... where **field** is `status.state` or `labels.[KEY]`, and `[KEY]` is a label key. **value** can be `*` to match all values. `status.state` can be either `ACTIVE` or `NON_ACTIVE`. Only the logical `AND` operator is supported; space-separated items are treated as having an implicit `AND` operator. Example filter: status.state = ACTIVE AND labels.env = staging AND labels.starred = *
A list of jobs in a project.
Output-only. Jobs list.
Optional. This token is included in the response if there are more results to fetch. To fetch additional results, provide this value as the `page_token` in a subsequent <code>ListJobsRequest</code>.
Submits a job to a cluster.
A request to submit a job.
Required. The ID of the Google Cloud Platform project that the job belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The job resource.
Updates a job in a project.
A request to update a job.
Required. The ID of the Google Cloud Platform project that the job belongs to.
Required. The Cloud Dataproc region in which to handle the request.
Required. The job ID.
Required. The changes to the job.
Required. Specifies the path, relative to <code>Job</code>, of the field to update. For example, to update the labels of a Job the <code>update_mask</code> parameter would be specified as <code>labels</code>, and the `PATCH` request body would specify the new value. <strong>Note:</strong> Currently, <code>labels</code> is the only field that can be updated.
Specifies the type and number of accelerator cards attached to the instances of an instance group (see [GPUs on Compute Engine](/compute/docs/gpus/)).
Used in:
Full URL, partial URI, or short name of the accelerator type resource to expose to this instance. See [Google Compute Engine AcceleratorTypes]( /compute/docs/reference/beta/acceleratorTypes) Examples * `https://www.googleapis.com/compute/beta/projects/[project_id]/zones/us-east1-a/acceleratorTypes/nvidia-tesla-k80` * `projects/[project_id]/zones/us-east1-a/acceleratorTypes/nvidia-tesla-k80` * `nvidia-tesla-k80`
The number of the accelerator cards of this type exposed to this instance.
Describes the identifying information, config, and status of a cluster of Google Compute Engine instances.
Used as response type in: ClusterController.GetCluster
Used as field type in: , ,
Required. The Google Cloud Platform project ID that the cluster belongs to.
Required. The cluster name. Cluster names within a project must be unique. Names of deleted clusters can be reused.
Required. The cluster config. Note that Cloud Dataproc may set default values, and values may change when clusters are updated.
Optional. The labels to associate with this cluster. 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 cluster.
Output-only. Cluster status.
Output-only. The previous cluster status.
Output-only. A cluster UUID (Unique Universal Identifier). Cloud Dataproc generates this value when it creates the cluster.
Contains cluster daemon metrics such as HDFS and YARN stats. **Beta Feature**: This report is available for testing purposes only. It may be changed before final release.
The cluster config.
Used in:
Optional. A Google Cloud Storage staging bucket used for sharing generated SSH keys and config. If you do not specify a staging bucket, Cloud Dataproc will determine an appropriate Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Google Compute Engine zone where your cluster is deployed, and then it will create and manage this project-level, per-location bucket for you.
Required. The shared Google Compute Engine config settings for all instances in a cluster.
Optional. The Google Compute Engine config settings for the master instance in a cluster.
Optional. The Google Compute Engine config settings for worker instances in a cluster.
Optional. The Google Compute Engine config settings for additional worker instances in a cluster.
Optional. The config settings for software inside the cluster.
Optional. Commands to execute on each node after config is completed. By default, executables are run on master and all worker nodes. You can test a node's `role` metadata to run an executable on a master or worker node, as shown below using `curl` (you can also use `wget`): ROLE=$(curl -H Metadata-Flavor:Google http://metadata/computeMetadata/v1/instance/attributes/dataproc-role) if [[ "${ROLE}" == 'Master' ]]; then ... master specific actions ... else ... worker specific actions ... fi
Contains cluster daemon metrics, such as HDFS and YARN stats. **Beta Feature**: This report is available for testing purposes only. It may be changed before final release.
Used in:
The HDFS metrics.
The YARN metrics.
Metadata describing the operation.
Output-only. Name of the cluster for the operation.
Output-only. Cluster UUID for the operation.
Output-only. Current operation status.
Output-only. The previous operation status.
Output-only. The operation type.
Output-only. Short description of operation.
Output-only. Labels associated with the operation
Output-only. Errors encountered during operation execution.
The status of the operation.
Used in:
Output-only. A message containing the operation state.
Output-only. A message containing the detailed operation state.
Output-only.A message containing any operation metadata details.
Output-only. The time this state was entered.
The operation state.
Used in:
Unused.
The operation has been created.
The operation is running.
The operation is done; either cancelled or completed.
The status of a cluster and its instances.
Used in:
Output-only. The cluster's state.
Output-only. Optional details of cluster's state.
Output-only. Time when this state was entered.
Output-only. Additional state information that includes status reported by the agent.
The cluster state.
Used in:
The cluster state is unknown.
The cluster is being created and set up. It is not ready for use.
The cluster is currently running and healthy. It is ready for use.
The cluster encountered an error. It is not ready for use.
The cluster is being deleted. It cannot be used.
The cluster is being updated. It continues to accept and process jobs.
Used in:
The cluster is known to be in an unhealthy state (for example, critical daemons are not running or HDFS capacity is exhausted). Applies to RUNNING state.
The agent-reported status is out of date (may occur if Cloud Dataproc loses communication with Agent). Applies to RUNNING state.
The location of diagnostic output.
Output-only. The Google Cloud Storage URI of the diagnostic output. The output report is a plain text file with a summary of collected diagnostics.
Specifies the config of disk options for a group of VM instances.
Used in:
Optional. Size in GB of the boot disk (default is 500GB).
Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and [HDFS](https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
Common config settings for resources of Google Compute Engine cluster instances, applicable to all instances in the cluster.
Used in:
Optional. The zone where the Google Compute Engine cluster will be located. On a create request, it is required in the "global" region. If omitted in a non-global Cloud Dataproc region, the service will pick a zone in the corresponding Compute Engine region. On a get request, zone will always be present. A full URL, partial URI, or short name are valid. Examples: * `https://www.googleapis.com/compute/v1/projects/[project_id]/zones/[zone]` * `projects/[project_id]/zones/[zone]` * `us-central1-f`
Optional. The Google Compute Engine network to be used for machine communications. Cannot be specified with subnetwork_uri. If neither `network_uri` nor `subnetwork_uri` is specified, the "default" network of the project is used, if it exists. Cannot be a "Custom Subnet Network" (see [Using Subnetworks](/compute/docs/subnetworks) for more information). A full URL, partial URI, or short name are valid. Examples: * `https://www.googleapis.com/compute/v1/projects/[project_id]/regions/global/default` * `projects/[project_id]/regions/global/default` * `default`
Optional. The Google Compute Engine subnetwork to be used for machine communications. Cannot be specified with network_uri. A full URL, partial URI, or short name are valid. Examples: * `https://www.googleapis.com/compute/v1/projects/[project_id]/regions/us-east1/sub0` * `projects/[project_id]/regions/us-east1/sub0` * `sub0`
Optional. If true, all instances in the cluster will only have internal IP addresses. By default, clusters are not restricted to internal IP addresses, and will have ephemeral external IP addresses assigned to each instance. This `internal_ip_only` restriction can only be enabled for subnetwork enabled networks, and all off-cluster dependencies must be configured to be accessible without external IP addresses.
Optional. The service account of the instances. Defaults to the default Google Compute Engine service account. Custom service accounts need permissions equivalent to the folloing IAM roles: * roles/logging.logWriter * roles/storage.objectAdmin (see https://cloud.google.com/compute/docs/access/service-accounts#custom_service_accounts for more information). Example: `[account_id]@[project_id].iam.gserviceaccount.com`
Optional. The URIs of service account scopes to be included in Google Compute Engine instances. The following base set of scopes is always included: * https://www.googleapis.com/auth/cloud.useraccounts.readonly * https://www.googleapis.com/auth/devstorage.read_write * https://www.googleapis.com/auth/logging.write If no scopes are specified, the following defaults are also provided: * https://www.googleapis.com/auth/bigquery * https://www.googleapis.com/auth/bigtable.admin.table * https://www.googleapis.com/auth/bigtable.data * https://www.googleapis.com/auth/devstorage.full_control
The Google Compute Engine tags to add to all instances (see [Tagging instances](/compute/docs/label-or-tag-resources#tags)).
The Google Compute Engine metadata entries to add to all instances (see [Project and instance metadata](https://cloud.google.com/compute/docs/storing-retrieving-metadata#project_and_instance_metadata)).
A Cloud Dataproc job for running [Apache Hadoop MapReduce](https://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/MapReduceTutorial.html) jobs on [Apache Hadoop YARN](https://hadoop.apache.org/docs/r2.7.1/hadoop-yarn/hadoop-yarn-site/YARN.html).
Used in:
Required. Indicates the location of the driver's main class. Specify either the jar file that contains the main class or the main class name. To specify both, add the jar file to `jar_file_uris`, and then specify the main class name in this property.
The HCFS URI of the jar file containing the main class. Examples: 'gs://foo-bucket/analytics-binaries/extract-useful-metrics-mr.jar' 'hdfs:/tmp/test-samples/custom-wordcount.jar' 'file:///home/usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar'
The name of the driver's main class. The jar file containing the class must be in the default CLASSPATH or specified in `jar_file_uris`.
Optional. The arguments to pass to the driver. Do not include arguments, such as `-libjars` or `-Dfoo=bar`, that can be set as job properties, since a collision may occur that causes an incorrect job submission.
Optional. Jar file URIs to add to the CLASSPATHs of the Hadoop driver and tasks.
Optional. HCFS (Hadoop Compatible Filesystem) URIs of files to be copied to the working directory of Hadoop drivers and distributed tasks. Useful for naively parallel tasks.
Optional. HCFS URIs of archives to be extracted in the working directory of Hadoop drivers and tasks. Supported file types: .jar, .tar, .tar.gz, .tgz, or .zip.
Optional. A mapping of property names to values, used to configure Hadoop. Properties that conflict with values set by the Cloud Dataproc API may be overwritten. Can include properties set in /etc/hadoop/conf/*-site and classes in user code.
Optional. The runtime log config for job execution.
A Cloud Dataproc job for running [Apache Hive](https://hive.apache.org/) queries on YARN.
Used in:
Required. The sequence of Hive queries to execute, specified as either an HCFS file URI or a list of queries.
The HCFS URI of the script that contains Hive queries.
A list of queries.
Optional. Whether to continue executing queries if a query fails. The default value is `false`. Setting to `true` can be useful when executing independent parallel queries.
Optional. Mapping of query variable names to values (equivalent to the Hive command: `SET name="value";`).
Optional. A mapping of property names and values, used to configure Hive. Properties that conflict with values set by the Cloud Dataproc API may be overwritten. Can include properties set in /etc/hadoop/conf/*-site.xml, /etc/hive/conf/hive-site.xml, and classes in user code.
Optional. HCFS URIs of jar files to add to the CLASSPATH of the Hive server and Hadoop MapReduce (MR) tasks. Can contain Hive SerDes and UDFs.
Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group.
Used in:
Optional. The number of VM instances in the instance group. For master instance groups, must be set to 1.
Optional. The list of instance names. Cloud Dataproc derives the names from `cluster_name`, `num_instances`, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from `SoftwareConfig.image_version`.
Optional. The Google Compute Engine machine type used for cluster instances. A full URL, partial URI, or short name are valid. Examples: * `https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2` * `projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2` * `n1-standard-2`
Optional. Disk option config settings.
Optional. Specifies that this instance group contains preemptible instances.
Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
Optional. The Google Compute Engine accelerator configuration for these instances. **Beta Feature**: This feature is still under development. It may be changed before final release.
A Cloud Dataproc job resource.
Used as response type in: JobController.CancelJob, JobController.GetJob, JobController.SubmitJob, JobController.UpdateJob
Used as field type in: , ,
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 <code>job_id</code>.
Required. Job information, including how, when, and where to run the job.
Required. The application/framework-specific portion of the job.
Job is a Hadoop job.
Job is a Spark job.
Job is a Pyspark job.
Job is a Hive job.
Job is a Pig job.
Job is a SparkSql job.
Output-only. The job status. Additional application-specific status information may be contained in the <code>type_job</code> and <code>yarn_applications</code> fields.
Output-only. The previous job status.
Output-only. 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.
Output-only. A URI pointing to the location of the stdout of the job's driver program.
Output-only. 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`.
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 scheduling configuration.
Cloud Dataproc job config.
Used in:
Required. The name of the cluster where the job will be submitted.
Output-only. A cluster UUID generated by the Cloud Dataproc service when the job is submitted.
Encapsulates the full scoping used to reference a job.
Used in:
Required. The ID of the Google Cloud Platform project that the job belongs to.
Optional. The job ID, which must be unique within the project. The job ID is generated by the server upon job submission or provided by the user as a means to perform retries without creating duplicate jobs. The ID must contain only letters (a-z, A-Z), numbers (0-9), underscores (_), or hyphens (-). The maximum length is 100 characters.
Job scheduling options. **Beta Feature**: These options are available for testing purposes only. They may be changed before final release.
Used in:
Optional. Maximum number of times per hour a driver may be restarted as a result of driver terminating with non-zero code before job is reported failed. A job may be reported as thrashing if driver exits with non-zero code 4 times within 10 minute window. Maximum value is 10.
Cloud Dataproc job status.
Used in:
Output-only. A state message specifying the overall job state.
Output-only. Optional job state details, such as an error description if the state is <code>ERROR</code>.
Output-only. The time when this state was entered.
Output-only. Additional state information, which includes status reported by the agent.
The job state.
Used in:
The job state is unknown.
The job is pending; it has been submitted, but is not yet running.
Job has been received by the service and completed initial setup; it will soon be submitted to the cluster.
The job is running on the cluster.
A CancelJob request has been received, but is pending.
Transient in-flight resources have been canceled, and the request to cancel the running job has been issued to the cluster.
The job cancellation was successful.
The job has completed successfully.
The job has completed, but encountered an error.
Job attempt has failed. The detail field contains failure details for this attempt. Applies to restartable jobs only.
Used in:
The Job is submitted to the agent. Applies to RUNNING state.
The Job has been received and is awaiting execution (it may be waiting for a condition to be met). See the "details" field for the reason for the delay. Applies to RUNNING state.
The agent-reported status is out of date, which may be caused by a loss of communication between the agent and Cloud Dataproc. If the agent does not send a timely update, the job will fail. Applies to RUNNING state.
A matcher that specifies categories of job states.
Used in:
Match all jobs, regardless of state.
Only match jobs in non-terminal states: PENDING, RUNNING, or CANCEL_PENDING.
Only match jobs in terminal states: CANCELLED, DONE, or ERROR.
The runtime logging config of the job.
Used in: , , , ,
The per-package log levels for the driver. This may include "root" package name to configure rootLogger. Examples: 'com.google = FATAL', 'root = INFO', 'org.apache = DEBUG'
The Log4j level for job execution. When running an [Apache Hive](http://hive.apache.org/) job, Cloud Dataproc configures the Hive client to an equivalent verbosity level.
Used in:
Level is unspecified. Use default level for log4j.
Use ALL level for log4j.
Use TRACE level for log4j.
Use DEBUG level for log4j.
Use INFO level for log4j.
Use WARN level for log4j.
Use ERROR level for log4j.
Use FATAL level for log4j.
Turn off log4j.
Specifies the resources used to actively manage an instance group.
Used in:
Output-only. The name of the Instance Template used for the Managed Instance Group.
Output-only. The name of the Instance Group Manager for this group.
Specifies an executable to run on a fully configured node and a timeout period for executable completion.
Used in:
Required. Google Cloud Storage URI of executable file.
Optional. Amount of time executable has to complete. Default is 10 minutes. Cluster creation fails with an explanatory error message (the name of the executable that caused the error and the exceeded timeout period) if the executable is not completed at end of the timeout period.
A Cloud Dataproc job for running [Apache Pig](https://pig.apache.org/) queries on YARN.
Used in:
Required. The sequence of Pig queries to execute, specified as an HCFS file URI or a list of queries.
The HCFS URI of the script that contains the Pig queries.
A list of queries.
Optional. Whether to continue executing queries if a query fails. The default value is `false`. Setting to `true` can be useful when executing independent parallel queries.
Optional. Mapping of query variable names to values (equivalent to the Pig command: `name=[value]`).
Optional. A mapping of property names to values, used to configure Pig. Properties that conflict with values set by the Cloud Dataproc API may be overwritten. Can include properties set in /etc/hadoop/conf/*-site.xml, /etc/pig/conf/pig.properties, and classes in user code.
Optional. HCFS URIs of jar files to add to the CLASSPATH of the Pig Client and Hadoop MapReduce (MR) tasks. Can contain Pig UDFs.
Optional. The runtime log config for job execution.
A Cloud Dataproc job for running [Apache PySpark](https://spark.apache.org/docs/0.9.0/python-programming-guide.html) applications on YARN.
Used in:
Required. The HCFS URI of the main Python file to use as the driver. Must be a .py file.
Optional. The arguments to pass to the driver. Do not include arguments, such as `--conf`, that can be set as job properties, since a collision may occur that causes an incorrect job submission.
Optional. HCFS file URIs of Python files to pass to the PySpark framework. Supported file types: .py, .egg, and .zip.
Optional. HCFS URIs of jar files to add to the CLASSPATHs of the Python driver and tasks.
Optional. HCFS URIs of files to be copied to the working directory of Python drivers and distributed tasks. Useful for naively parallel tasks.
Optional. HCFS URIs of archives to be extracted in the working directory of .jar, .tar, .tar.gz, .tgz, and .zip.
Optional. A mapping of property names to values, used to configure PySpark. Properties that conflict with values set by the Cloud Dataproc API may be overwritten. Can include properties set in /etc/spark/conf/spark-defaults.conf and classes in user code.
Optional. The runtime log config for job execution.
A list of queries to run on a cluster.
Used in: , ,
Required. The queries to execute. You do not need to terminate a query with a semicolon. Multiple queries can be specified in one string by separating each with a semicolon. Here is an example of an Cloud Dataproc API snippet that uses a QueryList to specify a HiveJob: "hiveJob": { "queryList": { "queries": [ "query1", "query2", "query3;query4", ] } }
Specifies the selection and config of software inside the cluster.
Used in:
Optional. The version of software inside the cluster. It must match the regular expression `[0-9]+\.[0-9]+`. If unspecified, it defaults to the latest version (see [Cloud Dataproc Versioning](/dataproc/versioning)).
Optional. The properties to set on daemon config files. Property keys are specified in `prefix:property` format, such as `core:fs.defaultFS`. The following are supported prefixes and their mappings: * capacity-scheduler: `capacity-scheduler.xml` * core: `core-site.xml` * distcp: `distcp-default.xml` * hdfs: `hdfs-site.xml` * hive: `hive-site.xml` * mapred: `mapred-site.xml` * pig: `pig.properties` * spark: `spark-defaults.conf` * yarn: `yarn-site.xml` For more information, see [Cluster properties](/dataproc/docs/concepts/cluster-properties).
A Cloud Dataproc job for running [Apache Spark](http://spark.apache.org/) applications on YARN.
Used in:
Required. The specification of the main method to call to drive the job. Specify either the jar file that contains the main class or the main class name. To pass both a main jar and a main class in that jar, add the jar to `CommonJob.jar_file_uris`, and then specify the main class name in `main_class`.
The HCFS URI of the jar file that contains the main class.
The name of the driver's main class. The jar file that contains the class must be in the default CLASSPATH or specified in `jar_file_uris`.
Optional. The arguments to pass to the driver. Do not include arguments, such as `--conf`, that can be set as job properties, since a collision may occur that causes an incorrect job submission.
Optional. HCFS URIs of jar files to add to the CLASSPATHs of the Spark driver and tasks.
Optional. HCFS URIs of files to be copied to the working directory of Spark drivers and distributed tasks. Useful for naively parallel tasks.
Optional. HCFS URIs of archives to be extracted in the working directory of Spark drivers and tasks. Supported file types: .jar, .tar, .tar.gz, .tgz, and .zip.
Optional. A mapping of property names to values, used to configure Spark. Properties that conflict with values set by the Cloud Dataproc API may be overwritten. Can include properties set in /etc/spark/conf/spark-defaults.conf and classes in user code.
Optional. The runtime log config for job execution.
A Cloud Dataproc job for running [Apache Spark SQL](http://spark.apache.org/sql/) queries.
Used in:
Required. The sequence of Spark SQL queries to execute, specified as either an HCFS file URI or as a list of queries.
The HCFS URI of the script that contains SQL queries.
A list of queries.
Optional. Mapping of query variable names to values (equivalent to the Spark SQL command: SET `name="value";`).
Optional. A mapping of property names to values, used to configure Spark SQL's SparkConf. Properties that conflict with values set by the Cloud Dataproc API may be overwritten.
Optional. HCFS URIs of jar files to be added to the Spark CLASSPATH.
Optional. The runtime log config for job execution.
A YARN application created by a job. Application information is a subset of <code>org.apache.hadoop.yarn.proto.YarnProtos.ApplicationReportProto</code>. **Beta Feature**: This report is available for testing purposes only. It may be changed before final release.
Used in:
Required. The application name.
Required. The application state.
Required. The numerical progress of the application, from 1 to 100.
Optional. The HTTP URL of the ApplicationMaster, HistoryServer, or TimelineServer that provides application-specific information. The URL uses the internal hostname, and requires a proxy server for resolution and, possibly, access.
The application state, corresponding to <code>YarnProtos.YarnApplicationStateProto</code>.
Used in:
Status is unspecified.
Status is NEW.
Status is NEW_SAVING.
Status is SUBMITTED.
Status is ACCEPTED.
Status is RUNNING.
Status is FINISHED.
Status is FAILED.
Status is KILLED.