Shell Action Parameters
Table 7.24. Shell Action, General Parameters
| Parameter Name | Description | Additional Information | Example |
|---|---|---|---|
| Exec | Path to the script file or the shell command. |
/user/ambari-qa/linecount.sh (where linecount.sh contains a script that does a specific operation) Or echo "NumberOfLines=`hadoop fs -cat $1 | wc -l`" | |
| Job XML | You can select one or more job.xml files to pass Shell configuration elements. | The configuration file that specifies the variables used for the Shell action in the workflow. Can be overwritten or replaced by entries under the Configuration section. | |
| Environment Variable |
Table 7.25. Shell Action, Transition Parameters
| Parameter Name | Description | Additional Information | Default Setting |
|---|---|---|---|
| Error To | Indicates what action to take if the action errors out. | You can modify this setting in the dialog box or by modifying the workflow graph. | Defaults to kill node, but can be changed. |
| OK To | Indicates what node to transition to if the action succeeds. | You can modify this setting in the dialog box or by modifying the workflow graph. | Defaults to the next node in the workflow. |
Table 7.26. Shell Action, Advanced Properties Parameters
| Parameter Name | Description | Additional Information | Example |
|---|---|---|---|
| Resource Manager | Master node that arbitrates all the available cluster resources among the competing applications. | The default setting is discovered from the cluster configuration. | ${resourceManager} |
| Name Node | Manages the file system metadata. | Keeps the directory tree of all files in the file system, and tracks where across the cluster the file data is kept. Clients contact NameNode for file metadata or file modifications. | ${nameNode} |
| File | Select any files that you want to make available to the Java action when the workflow runs. | /path/file | |
| Archive | Select any archives that you want to make available to the Java action when the workflow runs. | /path/archived-data-files | |
| Prepare | Select mkdir or delete and identify any HDFS paths to create or delete before starting the job. | Use delete to do file cleanup prior to job execution. Enables Oozie to retry a job if there is a transient failure (the job output directory must not exist prior to job start). If the path is to a directory: delete deletes all content recursively and then deletes the directory. mkdir creates all missing directories in the path. | |
| Arg | Identify any arguments to be passed to the shell script. | The value of each arg element is treated as a single argument, even if there are white spaces, and the values are passed to the main method in order. |
Table 7.27. Shell Action, Configuration Parameters
| Parameter Name | Description | Additional Information | Example |
|---|---|---|---|
| Name and Value | The name/value pair can be used instead of a job.xml file or can override parameters set in the job.xml file. |
Used to specify formal parameters. If the name and value are specified, the user can override the values from the Submit dialog box. Can be parameterized (templatized) using EL expressions. | |
| Capture Output | Indicates whether or not Oozie will capture output of the STDOUT of the shell command execution. Command output must be in Java Properties file format if another action will pick it up. | Useful if the output of the shell command needs to be used from within decision nodes. |