ADDJOBFLOWSTEPS()`¶

About AddJobFlowSteps¶

AddJobFlowSteps adds new steps to a running cluster. A maximum of 256 steps are allowed in each job flow.

If your cluster is long-running (such as a Hive data warehouse) or complex, you may require more than 256 steps to process your data. You can bypass the 256-step limitation in various ways, including using SSH to connect to the master node and submitting queries directly to the software running on the master node, such as Hive and Hadoop.

A step specifies the location of a JAR file stored either on the master node of the cluster or in Amazon S3. Each step is performed by the main function of the main class of the JAR file. The main class can be specified either in the manifest of the JAR or by using the MainFunction parameter of the step.

Amazon EMR executes each step in the order listed. For a step to be considered complete, the main function must exit with a zero exit code and all Hadoop jobs started while the step was running must have completed and run successfully.

You can only add steps to a cluster that is in one of the following states: STARTING, BOOTSTRAPPING, RUNNING, or WAITING.

The string values passed into HadoopJarStep object cannot exceed a total of 10240 characters.

Method Signature¶

IMPORTING¶

Required arguments:¶

`iv_jobflowid` `TYPE /AWS1/EMRXMLSTRINGMAXLEN256` `/AWS1/EMRXMLSTRINGMAXLEN256`¶

A string that uniquely identifies the job flow. This identifier is returned by RunJobFlow and can also be obtained from ListClusters.

`it_steps` `TYPE /AWS1/CL_EMRSTEPCONFIG=>TT_STEPCONFIGLIST` `TT_STEPCONFIGLIST`¶

A list of StepConfig to be executed by the job flow.

Optional arguments:¶

`iv_executionrolearn` `TYPE /AWS1/EMRARNTYPE` `/AWS1/EMRARNTYPE`¶

The Amazon Resource Name (ARN) of the runtime role for a step on the cluster. The runtime role can be a cross-account IAM role. The runtime role ARN is a combination of account ID, role name, and role type using the following format: arn:partition:service:region:account:resource.

For example, arn:aws:IAM::1234567890:role/ReadOnly is a correctly formatted runtime role ARN.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_emraddjobflowstepsout` `/AWS1/CL_EMRADDJOBFLOWSTEPSOUT`¶

Domain /AWS1/RT_ACCOUNT_ID

Primitive Type NUMC

Examples¶

Syntax Example¶

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->/aws1/if_emr~addjobflowsteps(
  it_steps = VALUE /aws1/cl_emrstepconfig=>tt_stepconfiglist(
    (
      new /aws1/cl_emrstepconfig(
        io_hadoopjarstep = new /aws1/cl_emrhadoopjarstepcfg(
          it_args = VALUE /aws1/cl_emrxmlstringlist_w=>tt_xmlstringlist(
            ( new /aws1/cl_emrxmlstringlist_w( |string| ) )
          )
          it_properties = VALUE /aws1/cl_emrkeyvalue=>tt_keyvaluelist(
            (
              new /aws1/cl_emrkeyvalue(
                iv_key = |string|
                iv_value = |string|
              )
            )
          )
          iv_jar = |string|
          iv_mainclass = |string|
        )
        iv_actiononfailure = |string|
        iv_name = |string|
      )
    )
  )
  iv_executionrolearn = |string|
  iv_jobflowid = |string|
).

This is an example of reading all possible response values

LOOP AT lo_result->get_stepids( ) into lo_row.
  lv_xmlstringmaxlen256 = lo_row_1->get_value( ).
ENDLOOP.

/AWS1/CL_EMR=>ADDJOBFLOWSTEPS()¶