Arbiter is a utility for generating XML Oozie workflows from a YAML specification.

Read the blog post that introduced Arbiter on Code as Craft, Etsy's engineering blog.

There is a mailing list for this project at https://groups.google.com/forum/#!forum/arbiter-oozie. If you have questions or suggestions for the project send them here!

1. Configuration driven: The mapping of the YAML workflow definition to the generated XML is highly configurable.
2. 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.

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.

Pre-built Arbiter JAR files are also available in Maven Central:

<dependency>
  <groupId>com.etsy</groupId>
  <artifactId>arbiter</artifactId>
  <version>0.5.0</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.

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]