gcloud_alpha_dataproc_workflow-templates_add-job_pyspark (1)

NAME

gcloud alpha dataproc workflow-templates add-job pyspark - add a PySpark job to the workflow template

SYNOPSIS

gcloud alpha dataproc workflow-templates add-job pyspark PY_FILE --step-id=STEP_ID --workflow-template=WORKFLOW_TEMPLATE [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY_FILE,...]] [--region=REGION] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...]

DESCRIPTION

(ALPHA) Add a PySpark job to the workflow template.

POSITIONAL ARGUMENTS

PY_FILE

Main .py file to run as the driver.

[-- JOB_ARGS ...]

Arguments to pass to the driver.
The '--' argument must be specified between gcloud specific args on the left and JOB_ARGS on the right.

REQUIRED FLAGS

--step-id=STEP_ID

The step ID of the job in the workflow template.

--workflow-template=WORKFLOW_TEMPLATE

The dataproc workflow template ID.

OPTIONAL FLAGS

--archives=[ARCHIVE,...]

Comma separated list of archives to be provided to the job. must be one of the following file formats: .zip, .tar, .tar.gz, or .tgz.

--driver-log-levels=[PACKAGE=LEVEL,...]

List of key value pairs to configure driver logging, where key is a package and value is the log4j log level. For example: root=FATAL,com.example=INFO

--files=[FILE,...]

Comma separated list of files to be provided to the job.

--jars=[JAR,...]

Comma separated list of jar files to be provided to the executor and driver classpaths.

--labels=[KEY=VALUE,...]

List of label KEY=VALUE pairs to add.
Keys must start with a lowercase character and contain only hyphens (-), underscores (_), lowercase characters, and numbers. Values must contain only hyphens (-), underscores (_), lowercase characters, and numbers.

--properties=[PROPERTY=VALUE,...]

List of key value pairs to configure PySpark. For a list of available properties, see: spark.apache.org/docs/latest/configuration.html#available-properties

--py-files=[PY_FILE,...]

Comma separated list of Python files to be provided to the job. Must be one of the following file formats ".py, .zip, or .egg".

--region=REGION

Cloud Dataproc region to use. Each Cloud Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute Engine zones inside the region. The default value of global is a special multi-region namespace which is capable of deploying instances into all Compute Engine zones globally, and is disjoint from other Cloud Dataproc regions. Overrides the default dataproc/region property value for this command invocation.

--start-after=STEP_ID,[STEP_ID,...]

(Optional) List of step IDs to start this job after.

GCLOUD WIDE FLAGS

These flags are available to all commands: --account, --configuration, --flags-file, --flatten, --format, --help, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details.

NOTES

This command is currently in ALPHA and may change without notice. If this command fails with API permission errors despite specifying the right project, you will have to apply for early access and have your projects registered on the API whitelist to use it. To do so, contact Support at cloud.google.com/support These variants are also available:

$ gcloud dataproc workflow-templates add-job pyspark $ gcloud beta dataproc workflow-templates add-job pyspark