Apache Oozie: Difference between revisions
added Category:Workflow technology using HotCat |
m →top: changed {{Notability}} to {{Notability|Products}} & general fixes using AWB |
||
| Line 1: | Line 1: | ||
{{multiple issues| |
{{multiple issues| |
||
{{notability|date=January 2013}} |
{{notability|Products|date=January 2013}} |
||
{{primary sources|date=January 2013}} |
{{primary sources|date=January 2013}} |
||
}} |
}} |
||
Revision as of 15:55, 31 December 2016
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
| Repository | |
|---|---|
| Website | oozie |
Apache Oozie is a server-based workflow scheduling system to manage Hadoop jobs.
Workflows in Oozie are defined as a collection of control flow and action nodes in a directed acyclic graph. Control flow nodes define the beginning and the end of a workflow (start, end and failure nodes) as well as a mechanism to control the workflow execution path (decision, fork and join nodes). Action nodes are the mechanism by which a workflow triggers the execution of a computation/processing task. Oozie provides support for different types of actions including Hadoop MapReduce, Hadoop distributed file system operations, Pig, SSH, and email. Oozie can also be extended to support additional types of actions.
Oozie workflows can be parameterised using variables such as ${inputDir} within the workflow definition. When submitting a workflow job, values for the parameters must be provided. If properly parameterized (using different output directories), several identical workflow jobs can run concurrently.
Oozie is implemented as a Java web application that runs in a Java servlet container and is distributed under the Apache License 2.0.
Editors
References
- ^ Mahran, Ahmed (30 October 2015). "Oozie Plugin for Eclipse". www.infoq.com. InfoQ. Retrieved 30 October 2015.