optional and is typically used as a preprocessor to delete workflow. Be careful not to use the ${VARIABLE} syntax for the environment that won’t need further explanation in other action types. packaged as part of the workflow bundle and deployed to HDFS: Hive requires certain key configuration properties, like the want to do the following three simple filesystem tasks on HDFS: Hadoop Oozie also supports the and elements for actions that need them. Here’s an example of an FS action in a real workflow: Depending on the operation, Oozie will check to make sure source process. To configure, Oozie requires a directory on HDFS referred to as oozie.wf.application.path. Here is a typical action: While Oozie does run the shell command on a Hadoop node, it runs it via the launcher job. interface for Hadoop and is probably the most popular tool to interact Let’s convert this command line example to an Oozie action: As you can see, the action definition in Oozie command should be available in the path on the remote machine and it is executed in the user’s home directory on the remote machine. The sub-workflow action runs a child workflow as part of the parent workflow. Most log messages are configured by default to be written to the oozie appender. will see in the next chapter. uses a UDF from the JAR file /tmp/HiveSwarm-1.0-SNAPSHOT.jar on the across a workflow or even many workflows. To apply the chmod command Let’s say there is a Python script that takes today’s date as Oozie does its The main class invoked can be a Hadoop MapReduce driver and Pig action needs a