gcloud_dataproc_workflow-templates_add-job_hadoop (1)
NAME
- gcloud dataproc workflow-templates add-job hadoop - add a hadoop job to the workflow template
SYNOPSIS
-
gcloud dataproc workflow-templates add-job hadoop --step-id=STEP_ID --workflow-template=WORKFLOW_TEMPLATE (--class=MAIN_CLASS | --jar=MAIN_JAR) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...]
DESCRIPTION
POSITIONAL ARGUMENTS
-
- [-- JOB_ARGS ...]
-
The 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.
-
Exactly one of these must be specified:
-
- --class=MAIN_CLASS
-
The class containing the main method of the driver. Must be in a provided jar or
jar that is already on the classpath
- --jar=MAIN_JAR
-
The HCFS URI of jar file containing the driver jar.
-
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,...]
-
A list of package to log4j log level pairs to configure driver logging. 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 MR 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,...]
-
A list of key value pairs to configure Hadoop.
- --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
These variants are also available:
- $ gcloud alpha dataproc workflow-templates add-job hadoop $ gcloud beta dataproc workflow-templates add-job hadoop