Arbiter is a utility for generating XML Oozie workflows from a YAML specification.
- Configuration driven: The mapping of the YAML workflow definition to the generated XML is highly configurable.
- Automatic dependency resolution and parallelism: Arbiter workflows are specified in terms of the dependencies between actions, rather than requiring the author to manually specify the flow. Arbiter will order the workflow actions to satisfy the dependencies as well as insert fork/join pairs to run actions in parallel when possible.
- Conditional execution of an action: An action can have condition which when evaluated false will skip the execution of that particular action.
- Global configurations and credentials block: Configuration YAML and workflow YAML can specify global configuration section and credentials block for the oozie workflow
- Tags with attributes: Now actions like FS are possible.
- Prepare block config for actions
- Recursively traverse and compile YAML files for config as well as workflow files
- Support for retry-max and retry-interval attributes.
Arbiter requires at least Java 7.
Arbiter is built with Maven. Run
mvn clean package to build an uber-JAR suitable for use in running Arbiter.
<dependency> <groupId>net.achalaggarwal.arbiter</groupId> <artifactId>arbiter</artifactId> <version>0.1</version> </dependency>
Before writing workflows with Arbiter, you must define at least one configuration file. See Configuration for details on writing a configuration file.
See Workflow Definition for details on writing workflows with Arbiter.
Command Line Options
|-c||Specifies the path to a configuration file/folder. Required.|
|-l||Specifies the path to a low-priority configuration file/folder. Low priority configurations will be overridden by standard configurations if they define overlapping settings. Optional.|
|-i||Specifies the path to a YAML workflow definition folder to process. Required.|
|-g ||Enables generating a image of the workflow graph using Graphviz. The
|-h||Prints a usage message|
First build an Arbiter uber-JAR as described in the Building section above. Arbiter can then be invoked like so:
java -jar arbiter.jar [OPTIONS]
Arbiter will recursively read config files and process workflow YAML files and will generate corresponding XML file with same name. If -g is provided while running then it will generate dot files inside dot directory