Submit Job

dataproc.submit_job
ActionGoogle Cloudconnection required

Calls Dataproc POST /regions/{r}/jobs:submit.

Submit a PySpark, Spark SQL or Hive job to a Dataproc cluster.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud Dataproc
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, region
Resolved by
config.connection_id, else node.connection_id

Configuration

7 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
region
GCP region (overrides connection).
stringNo———
cluster_name
Target cluster.
stringYes———
job_type
Job kind — Dataproc accepts only the listed values.
stringNopysparkone of "pyspark", "spark_sql", "hive"—
main_python_file_uri
gs:// URI of the PySpark driver (pyspark).
stringNo———
args
Driver arguments as JSON array (pyspark).
arrayNo—array of string—
query
SQL / HiveQL text (spark_sql, hive).
stringNo———
  • At least one of main_python_file_uri, query must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "job_type": "pyspark"
}

Output

One shape.

result

FieldTypeExample
job_id
string—
state
string—
cluster_name
string—
done
boolean—
{
  "cluster_name": "",
  "done": false,
  "job_id": "",
  "state": ""
}

See Submit Job run in a workflow.

In a technical demo we add the Google Cloud Dataproc connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.