|
|
@@ -1,481 +1,1418 @@
|
|
|
-<h1><a name="OozieEditorandDashboard-IntroducingOozieEditor%2FDashboard"></a>Introducing Oozie Editor/Dashboard</h1>
|
|
|
-
|
|
|
-<p>The Oozie Editor/Dashboard application allows you to define Oozie workflow and coordinator applications, run workflow and coordinator jobs, and view the status of jobs. For information about Oozie, see <a href="http://archive.cloudera.com/cdh4/cdh/4/oozie/">Oozie Documentation</a>.</p>
|
|
|
-
|
|
|
-<p>A workflow application is a collection of actions arranged in a directed acyclic graph (DAG). It includes control flow nodes (start, end, fork, join, decision, and kill) and action nodes (MapReduce, Streaming, Java, Pig, Hive, Sqoop, Shell, Ssh, DistCp, Fs, Email, Sub-workflow, and Generic).</p>
|
|
|
-
|
|
|
-<p>A coordinator application allows you to define and execute recurrent and interdependent workflow jobs. The coordinator application defines the conditions under which the execution of workflows can occur.</p>
|
|
|
-
|
|
|
-
|
|
|
-
|
|
|
-<h2><a name="OozieEditorandDashboard-Contents"></a>Contents</h2>
|
|
|
-
|
|
|
-<style type='text/css'>/*<![CDATA[*/
|
|
|
-div.rbtoc1360779583763 {margin-left: 1.5em;padding: 0px;}
|
|
|
-div.rbtoc1360779583763 ul {margin-left: 0px;padding-left: 20px;}
|
|
|
-div.rbtoc1360779583763 li {margin-left: 0px;padding-left: 0px;}
|
|
|
-
|
|
|
-/*]]>*/</style><div class='rbtoc1360779583763'>
|
|
|
-<ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-IntroducingOozieEditor%2FDashboard'>Introducing Oozie Editor/Dashboard</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-Oozie%26nbsp%3BEditor%2FDashboard%26nbsp%3BInstallationandConfiguration'>Oozie Editor/Dashboard Installation and Configuration</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-StartingOozie%26nbsp%3BEditor%2FDashboard'>Starting Oozie Editor/Dashboard</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-InstallingOozieEditor%2FDashboardSamples'>Installing Oozie Editor/Dashboard Samples</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-FilteringListsinOozieEditor%2FDashboard'>Filtering Lists in Oozie Editor/Dashboard</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-PermissionsinOozieEditor%2FDashboard'>Permissions in Oozie Editor/Dashboard</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-OozieDashboard'>Oozie Dashboard</a></li>
|
|
|
-<ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-Workflows'>Workflows</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-Coordinators'>Coordinators</a></li>
|
|
|
-</ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-WorkflowManager'>Workflow Manager</a></li>
|
|
|
-<ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-InstallingtheSampleWorkflows'>Installing the Sample Workflows</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-OpeningaWorkflow'>Opening a Workflow</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-CreatingaWorkflow'>Creating a Workflow</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-ImportingaWorkflow'>Importing a Workflow</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-SubmittingaWorkflow'>Submitting a Workflow</a></li>
|
|
|
-<ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-SuspendingaRunningJob'>Suspending a Running Job</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-ResumingaSuspendedJob'>Resuming a Suspended Job</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-RerunningaWorkflow'>Rerunning a Workflow</a></li>
|
|
|
-</ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-SchedulingaWorkflow'>Scheduling a Workflow</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-EditingaWorkflow'>Editing a Workflow</a></li>
|
|
|
-<ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-ActionNodes'>Action Nodes</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-ControlNodes'>Control Nodes</a></li>
|
|
|
-</ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-UploadingWorkflowFiles'>Uploading Workflow Files</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-EditingWorkflowProperties'>Editing Workflow Properties</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-DisplayingtheHistoryofaWorkflow'>Displaying the History of a Workflow</a></li>
|
|
|
-</ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-CoordinatorManager'>Coordinator Manager</a></li>
|
|
|
-<ul>
|
|
|
- <li><a href='#OozieEditorandDashboard-OpeningaCoordinator'>Opening a Coordinator</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-CreatingaCoordinator'>Creating a Coordinator</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-SubmittingaCoordinator'>Submitting a Coordinator</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-EditingaCoordinator'>Editing a Coordinator</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-CreatingaDataset'>Creating a Dataset</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-DisplayingDatasets'>Displaying Datasets</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-EditingaDataset'>Editing a Dataset</a></li>
|
|
|
- <li><a href='#OozieEditorandDashboard-DisplayingtheHistoryofaCoordinator'>Displaying the History of a Coordinator</a></li>
|
|
|
-</ul>
|
|
|
-</ul></div>
|
|
|
-
|
|
|
-<h1><a name="OozieEditorandDashboard-Oozie%26nbsp%3BEditor%2FDashboard%26nbsp%3BInstallationandConfiguration"></a>Oozie Editor/Dashboard Installation and Configuration</h1>
|
|
|
-
|
|
|
-<p>Oozie Editor/Dashboard is one of the applications that is installed as part of Hue. For information about installing and configuring Hue, see <a href="https://ccp.cloudera.com/display/CDH4DOC/Hue+Installation">Hue Installation</a>.</p>
|
|
|
-
|
|
|
-<div class='panelMacro'><table class='noteMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/static/art/help/warning.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td><b>Note</b><br />In order to run DistCp, Streaming, Pig, Sqoop, and Hive jobs as part of a workflow, Oozie must be configured to use the Oozie ShareLib. See <a href="https://ccp.cloudera.com/display/CDH4DOC/Oozie+Installation">Oozie Installation</a>.</td></tr></table></div>
|
|
|
-
|
|
|
-<h1><a name="OozieEditorandDashboard-StartingOozie%26nbsp%3BEditor%2FDashboard"></a>Starting Oozie Editor/Dashboard</h1>
|
|
|
-
|
|
|
-<p>To start Oozie Editor/Dashboard, click the <b>Oozie Editor/Dashboard</b> icon (<span class="image-wrap" style=""><img src="/jobsub/static/help/images/23888164.png" width="24" style="border: 0px solid black"/></span>) in the navigation bar at the top of the Hue browser page. <b>Oozie Editor/Dashboard</b> opens with the following screens:</p>
|
|
|
-
|
|
|
-<ul>
|
|
|
- <li>Dashboard - shows the running and completed workflow and coordinator jobs. The screen is selected and opened to the Workflows page.</li>
|
|
|
- <li>Workflows - shows available workflows.</li>
|
|
|
- <li>Coordinators - shows available coordinators.</li>
|
|
|
- <li>History - shows a list of submitted jobs.</li>
|
|
|
-</ul>
|
|
|
-
|
|
|
-
|
|
|
-<h1><a name="OozieEditorandDashboard-InstallingOozieEditor%2FDashboardSamples"></a>Installing Oozie Editor/Dashboard Samples</h1>
|
|
|
-
|
|
|
-<p>The Oozie Editor/Dashboard sample workflows and coordinators can help you learn how to use Oozie Editor/Dashboard. To install the samples:</p>
|
|
|
-
|
|
|
-<ol>
|
|
|
- <li>Click the <b>Workflows</b> tab.</li>
|
|
|
- <li>Click the <b>Setup App</b> button. This action adds samples demonstrating all the types of actions to the Workflows Editor and one sample to the Coordinator Editor. It also creates workspaces and deployment directories required by the samples in /user/hue/oozie.</li>
|
|
|
-</ol>
|
|
|
-
|
|
|
-
|
|
|
-<h1><a name="OozieEditorandDashboard-FilteringListsinOozieEditor%2FDashboard"></a>Filtering Lists in Oozie Editor/Dashboard</h1>
|
|
|
-
|
|
|
-<p>The Dashboard, Workflows, Coordinators, and History screens contain lists of workflows, coordinators, and jobs. When you type in the Filter field on these screens, the lists are dynamically filtered to display only those rows containing text that matches the specified substring.</p>
|
|
|
-
|
|
|
-<h1><a name="OozieEditorandDashboard-PermissionsinOozieEditor%2FDashboard"></a>Permissions in Oozie Editor/Dashboard</h1>
|
|
|
-
|
|
|
-<p>In the Dashboard workflows and coordinators can only be viewed, submitted, and modified by its owner or a superuser.</p>
|
|
|
-
|
|
|
-<p>Editor permissions for performing actions on workflows and coordinators are summarized in the following table:</p>
|
|
|
-
|
|
|
-<style type="text/css">
|
|
|
-td.confluenceTd {
|
|
|
-border: #dddddd solid 1px;
|
|
|
-height: 36px;
|
|
|
-padding: 5px 10px;
|
|
|
-vertical-align: top;
|
|
|
-}
|
|
|
-th.confluenceTh {
|
|
|
-border: #dddddd solid 1px;
|
|
|
-height: 40px;
|
|
|
-padding: 5px 10px;
|
|
|
-vertical-align: center;
|
|
|
-}
|
|
|
-</style>
|
|
|
-
|
|
|
-<div class='table-wrap'>
|
|
|
-<table class='confluenceTable'><tbody>
|
|
|
-<tr>
|
|
|
-<th class='confluenceTh'> Action </th>
|
|
|
-<th class='confluenceTh'> Superuser or Owner <br class="atl-forced-newline" /> </th>
|
|
|
-<th class='confluenceTh'> All </th>
|
|
|
-</tr>
|
|
|
-<tr>
|
|
|
-<td class='confluenceTd'> View </td>
|
|
|
-<td class='confluenceTd'> Y </td>
|
|
|
-<td class='confluenceTd'> Only if "Is shared" is set <br class="atl-forced-newline" /> </td>
|
|
|
-</tr>
|
|
|
-<tr>
|
|
|
-<td class='confluenceTd'> Submit </td>
|
|
|
-<td class='confluenceTd'> Y </td>
|
|
|
-<td class='confluenceTd'> Only if "Is shared" is set <br class="atl-forced-newline" /> </td>
|
|
|
-</tr>
|
|
|
-<tr>
|
|
|
-<td class='confluenceTd'> Modify </td>
|
|
|
-<td class='confluenceTd'> Y </td>
|
|
|
-<td class='confluenceTd'> N </td>
|
|
|
-</tr>
|
|
|
-</tbody></table>
|
|
|
+<?xml version="1.0" encoding="UTF-8"?>
|
|
|
+<!DOCTYPE html
|
|
|
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
|
+<html lang="en-us" xml:lang="en-us">
|
|
|
+<head>
|
|
|
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
|
|
|
+<link rel="stylesheet" type="text/css" href="commonltr.css"/>
|
|
|
+<title>Oozie Editor and Dashboard</title>
|
|
|
+</head>
|
|
|
+<body id="topic_9"><a name="topic_9"><!-- --></a>
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+ <h1 class="title topictitle1">Oozie Editor and Dashboard </h1>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p">The Oozie Editor/Dashboard application allows you to define Oozie
|
|
|
+ workflow, coordinator, and bundle applications, run workflow, coordinator, and bundle jobs,
|
|
|
+ and view the status of jobs. For information about Oozie, see <a class="xref" href="http://archive.cloudera.com/cdh4/cdh/4/oozie/" target="_blank">Oozie Documentation</a>. </p>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="p">A <dfn class="term">workflow application</dfn> is a collection of actions arranged in
|
|
|
+ a directed acyclic graph (DAG). It includes two types of nodes:<a name="topic_9__ul_fyv_mnr_2k"><!-- --></a><ul class="ul" id="topic_9__ul_fyv_mnr_2k">
|
|
|
+ <li class="li">Control flow - start, end, fork, join, decision, and kill</li>
|
|
|
+
|
|
|
+ <li class="li">Action - <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_lvq_ch3_zj">MapReduce</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_zrd_gh3_zj">Streaming</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_abl_hh3_zj">Java</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_tvm_3h3_zj">Pig</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_lxq_3h3_zj">Hive</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_xb5_3h3_zj">Sqoop</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_xvw_3h3_zj">Shell</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_tnz_3h3_zj">Ssh</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_qsc_jh3_zj">DistCp</a>, <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_hx4_lh3_zj">Fs</a>, and <a class="xref" href="jobsub#concept_gt5_bh3_zj__section_qjt_lh3_zj">Email</a>) <p class="p">In order to run DistCp, Streaming, Pig, Sqoop, and Hive
|
|
|
+ jobs, Oozie must be configured to use the Oozie ShareLib. See Oozie Installation in <a class="xref" href="http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html" target="_blank">http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html</a>. </p>
|
|
|
+</li>
|
|
|
+
|
|
|
+ </ul>
|
|
|
+</div>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">A <dfn class="term">coordinator application</dfn> allows you to define and execute
|
|
|
+ recurrent and interdependent workflow jobs. The coordinator application defines the conditions
|
|
|
+ under which the execution of workflows can occur. </p>
|
|
|
+
|
|
|
+ <p class="p">A <dfn class="term">bundle application</dfn> allows you to batch a set of
|
|
|
+ coordinator applications. </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested1" xml:lang="en-US" lang="en-US" id="topic_9_1"><a name="topic_9_1"><!-- --></a>
|
|
|
+
|
|
|
+ <h2 class="title topictitle2">Oozie Editor/Dashboard Installation and
|
|
|
+ Configuration </h2>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p">Oozie Editor/Dashboard is one of the applications installed as part of
|
|
|
+ Hue. <span class="ph">For information about installing and configuring Hue,
|
|
|
+ see Hue Installation in <a class="xref" href="http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html" target="_blank">http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html</a>.</span></p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested1" xml:lang="en-US" lang="en-US" id="topic_9_2"><a name="topic_9_2"><!-- --></a>
|
|
|
+
|
|
|
+ <h2 class="title topictitle2">Starting Oozie Editor/Dashboard </h2>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p">Click the <strong class="ph b">Oozie Editor/Dashboard</strong> icon
|
|
|
+ (<img class="image" src="/static/art/help/icon_oozie_24.png"/>) in the navigation bar at the top of the Hue browser page. <strong class="ph b">Oozie Editor/Dashboard</strong> opens with the following screens: </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+ <li class="li"><a class="xref" href="#topic_9_6">Dashboard</a> - shows
|
|
|
+ the running and completed workflow, coordinator, and bundle jobs and information about
|
|
|
+ Oozie instrumentation and configuration. The screen is selected and opened to the
|
|
|
+ Workflows page.</li>
|
|
|
+
|
|
|
+ <li class="li"><a class="xref" href="#topic_9_7">Workflow Manager</a> - shows
|
|
|
+ available workflows and allows you to create and import workflows.</li>
|
|
|
+
|
|
|
+ <li class="li"><a class="xref" href="#topic_9_8">Coordinator Manager</a> - shows
|
|
|
+ available coordinators and allows you to create coordinators.</li>
|
|
|
+
|
|
|
+ <li class="li"><a class="xref" href="#concept_crd_ttp_wj">Bundle Manager</a> - shows available bundles and allows you to create bundles.</li>
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested1" xml:lang="en-US" lang="en-US" id="topic_9_3"><a name="topic_9_3"><!-- --></a>
|
|
|
+
|
|
|
+ <h2 class="title topictitle2">Installing Oozie Editor/Dashboard
|
|
|
+ Examples </h2>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+ <div class="note note"><span class="notetitle"><img src="/static/art/help/note.jpg"/>
|
|
|
+ <b>Note</b>:</span> You must be a superuser to perform this task.</div>
|
|
|
+
|
|
|
+
|
|
|
+ <a name="topic_9_3__ol_ugf_hjt_yj"><!-- --></a><ol class="ol" id="topic_9_3__ol_ugf_hjt_yj">
|
|
|
+ <li class="li">Click <a name="topic_9_3__d104e102"><!-- --></a><img class="image" id="topic_9_3__d104e102" src="/static/art/help/quick_start.png"/>. The Quick Start Wizard opens.</li>
|
|
|
+<li class="li">Click <strong class="ph b">Step 2:
|
|
|
+ Examples</strong>.</li>
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">Oozie Editor/Dashboard</strong>.</li>
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested1" xml:lang="en-US" lang="en-US" id="topic_9_4"><a name="topic_9_4"><!-- --></a>
|
|
|
+
|
|
|
+ <h2 class="title topictitle2">Filtering Lists in Oozie Editor/Dashboard </h2>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p">Many screens contain lists. When you type in the Filter field on
|
|
|
+ screens, the lists are dynamically filtered to display only those rows containing text that
|
|
|
+ matches the specified substring. </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested1" xml:lang="en-US" lang="en-US" id="topic_9_5"><a name="topic_9_5"><!-- --></a>
|
|
|
+
|
|
|
+ <h2 class="title topictitle2">Permissions in Oozie Editor/Dashboard
|
|
|
+ </h2>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p">In the Dashboard workflows, coordinators, and bundles can only be
|
|
|
+ viewed, submitted, and modified by their owner or a superuser. </p>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">Editor permissions for performing actions on workflows, coordinators,
|
|
|
+ and bundles are summarized in the following table: </p>
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" class="table" frame="hsides" border="1" rules="all">
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+ <thead class="thead" align="left">
|
|
|
+ <tr class="row">
|
|
|
+ <th class="entry" valign="top" width="33.33333333333333%" id="d15249e233">
|
|
|
+ <p class="p"> <strong class="ph b">Action</strong>
|
|
|
+ </p>
|
|
|
+
|
|
|
+ </th>
|
|
|
+
|
|
|
+ <th class="entry" valign="top" width="33.33333333333333%" id="d15249e242">
|
|
|
+ <p class="p"> <strong class="ph b">Superuser or Owner</strong>
|
|
|
+ </p>
|
|
|
+
|
|
|
+ </th>
|
|
|
+
|
|
|
+ <th class="entry" valign="top" width="33.33333333333333%" id="d15249e251">
|
|
|
+ <p class="p"> <strong class="ph b">All</strong>
|
|
|
+ </p>
|
|
|
+
|
|
|
+ </th>
|
|
|
+
|
|
|
+ </tr>
|
|
|
+
|
|
|
+ </thead>
|
|
|
+
|
|
|
+ <tbody class="tbody">
|
|
|
+ <tr class="row">
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e233 ">
|
|
|
+ <p class="p">View </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e242 ">
|
|
|
+ <p class="p">Y </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e251 ">
|
|
|
+ <p class="p">Only if "Is shared" is set </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ </tr>
|
|
|
+
|
|
|
+ <tr class="row">
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e233 ">
|
|
|
+ <p class="p">Submit </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e242 ">
|
|
|
+ <p class="p">Y </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e251 ">
|
|
|
+ <p class="p">Only if "Is shared" is set </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ </tr>
|
|
|
+
|
|
|
+ <tr class="row">
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e233 ">
|
|
|
+ <p class="p">Modify </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e242 ">
|
|
|
+ <p class="p">Y </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ <td class="entry" valign="top" width="33.33333333333333%" headers="d15249e251 ">
|
|
|
+ <p class="p">N </p>
|
|
|
+
|
|
|
+ </td>
|
|
|
+
|
|
|
+ </tr>
|
|
|
+
|
|
|
+ </tbody>
|
|
|
+
|
|
|
+ </table>
|
|
|
</div>
|
|
|
|
|
|
|
|
|
-<h1><a name="OozieEditorandDashboard-OozieDashboard"></a>Oozie Dashboard</h1>
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="topic concept nested1" id="concept_ms2_rzj_2k"><a name="concept_ms2_rzj_2k"><!-- --></a>
|
|
|
+ <h2 class="title topictitle2">Deleting and Restoring Workflows, Coordinators, and Bundles</h2>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+ <p class="p">You can move workflows, coordinators, and bundles to the trash and later restore or
|
|
|
+ permanently delete them.</p>
|
|
|
+
|
|
|
+ <div class="section" id="concept_ms2_rzj_2k__section_bvz_wzj_2k"><a name="concept_ms2_rzj_2k__section_bvz_wzj_2k"><!-- --></a><h3 class="title sectiontitle">Deleting Workflows, Coordinators, and Bundles</h3>
|
|
|
+
|
|
|
+ <a name="concept_ms2_rzj_2k__ol_wkz_yzj_2k"><!-- --></a><ol class="ol" id="concept_ms2_rzj_2k__ol_wkz_yzj_2k">
|
|
|
+ <li class="li">In a Manager screen, check the checkbox next to one or more workflows, coordinators or
|
|
|
+ bundles.</li>
|
|
|
+
|
|
|
+ <li class="li" id="concept_ms2_rzj_2k__li_dty_3gr_2k"><a name="concept_ms2_rzj_2k__li_dty_3gr_2k"><!-- --></a>Choose one of the following:<ul class="ul">
|
|
|
+ <li class="li"><span class="ph menucascade"><span class="ph uicontrol">Delete</span> > <span class="ph uicontrol">Move to trash</span></span></li>
|
|
|
+
|
|
|
+ <li class="li"><span class="ph menucascade"><span class="ph uicontrol">Delete</span> > <span class="ph uicontrol">Delete forever</span></span></li>
|
|
|
+
|
|
|
+ </ul>
|
|
|
+</li>
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="section" id="concept_ms2_rzj_2k__section_ecf_xzj_2k"><a name="concept_ms2_rzj_2k__section_ecf_xzj_2k"><!-- --></a><h3 class="title sectiontitle">Restoring Workflows, Coordinators, and Bundles</h3>
|
|
|
+
|
|
|
+ <a name="concept_ms2_rzj_2k__ol_ujf_dbk_2k"><!-- --></a><ol class="ol" id="concept_ms2_rzj_2k__ol_ujf_dbk_2k">
|
|
|
+ <li class="li" id="concept_ms2_rzj_2k__li_msc_mgr_2k"><a name="concept_ms2_rzj_2k__li_msc_mgr_2k"><!-- --></a>In a Manager screen, click <a name="concept_ms2_rzj_2k__image_e35_2bk_2k"><!-- --></a><img class="image" id="concept_ms2_rzj_2k__image_e35_2bk_2k" src="/static/art/help/trash.png"/>
|
|
|
+ <strong class="ph b">Trash</strong>.</li>
|
|
|
+
|
|
|
+ <li class="li">Check the checkbox next to one or more workflows, coordinators or bundles.</li>
|
|
|
+
|
|
|
+ <li class="li" id="concept_ms2_rzj_2k__li_ndg_mgr_2k"><a name="concept_ms2_rzj_2k__li_ndg_mgr_2k"><!-- --></a>Click <span class="ph uicontrol">Restore</span>.</li>
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested1" xml:lang="en-US" lang="en-US" id="topic_9_6"><a name="topic_9_6"><!-- --></a>
|
|
|
+
|
|
|
+ <h2 class="title topictitle2">Dashboard </h2>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p">The Dashboard shows a summary of the running and completed workflow,
|
|
|
+ coordinator, and bundle jobs. </p>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ You can view jobs for a period up to the last 30 days.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ You can filter the list by date (1, 7, 15, or 30 days) or status (Succeeded, Running, or Killed). The date and
|
|
|
+ status buttons are toggles.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_6_1"><a name="topic_9_6_1"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Workflows</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">Click the <strong class="ph b">Workflows</strong> tab to view the running and completed workflow jobs for the filters you have
|
|
|
+ specified.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+<p class="p">Click a workflow row in the Running or Completed table to view detailed information about that workflow job.
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <p class="p">In the left pane contains a link to the workflow and the variable values specified.<br/><a name="topic_9_6_1__image_xq2_stz_2k"><!-- --></a><img class="image" id="topic_9_6_1__image_xq2_stz_2k" src="/static/art/help/workflow.jpg"/><br/>
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+<p class="p">For the selected job, the following information is available in the right
|
|
|
+ area. </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Graph</strong> tab shows the workflow
|
|
|
+ DAG.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">
|
|
|
+ <strong class="ph b">Actions</strong> tab shows you details about the actions that
|
|
|
+ make up the workflow.<a name="topic_9_6_1__ul_pgz_3nt_4j"><!-- --></a><ul class="ul" id="topic_9_6_1__ul_pgz_3nt_4j">
|
|
|
+ <li class="li">Click the <strong class="ph b">Id</strong> link to see
|
|
|
+ additional details about the action.</li>
|
|
|
+
|
|
|
+ <li class="li">Click the <strong class="ph b">External Id</strong> link
|
|
|
+ to view the job in the Job Browser.</li>
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+ </li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Details</strong> tab shows job statistics
|
|
|
+ including start and end times.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Configuration</strong> tab shows selected
|
|
|
+ job configuration settings.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Logs</strong> tab shows log output
|
|
|
+ generated by the workflow job.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Definition</strong> tab shows the Oozie
|
|
|
+ workflow definition, as it appears in the <samp class="ph codeph">workflow.xml</samp> file (also linked under the application path properties in the
|
|
|
+ <strong class="ph b">Details</strong> tab and the <strong class="ph b">Configuration</strong> tab).</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+ <p class="p">For each action in the workflow you can:</p>
|
|
|
+
|
|
|
+ <a name="topic_9_6_1__ul_v4y_htz_2k"><!-- --></a><ul class="ul" id="topic_9_6_1__ul_v4y_htz_2k">
|
|
|
+ <li class="li">
|
|
|
+ <div class="p">Click the <a name="topic_9_6_1__image_u3d_ssz_2k"><!-- --></a><img class="image" id="topic_9_6_1__image_u3d_ssz_2k" src="/static/art/help/eye.png"/> icon to view the
|
|
|
+ action screen, which contains:<a name="topic_9_6_1__ul_edm_5sz_2k"><!-- --></a><ul class="ul" id="topic_9_6_1__ul_edm_5sz_2k">
|
|
|
+ <li class="li"><strong class="ph b">Details</strong> tab shows job statistics including start and end times.</li>
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Configuration</strong> tab shows the action configuration settings.</li>
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Child Jobs</strong> tab lists jobs generated by the action.</li>
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ </li>
|
|
|
+
|
|
|
+ <li class="li">
|
|
|
+ <p class="p">Click the <a name="topic_9_6_1__image_hwj_ktz_2k"><!-- --></a><img class="image" id="topic_9_6_1__image_hwj_ktz_2k" src="/static/art/help/log.png"/> icon to view the log
|
|
|
+ in the Job Browser. </p>
|
|
|
+
|
|
|
+ </li>
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_6_2"><a name="topic_9_6_2"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Coordinators</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">Click the <strong class="ph b">Coordinators</strong> tab to view the running and completed coordinator jobs for the filters you have
|
|
|
+ specified.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+<p class="p">For the selected job, the following information is available.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li">The <strong class="ph b">Calendar</strong> tab shows the timestamp of the job. Click the timestamp
|
|
|
+ to open the workflow DAG. </li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">The <strong class="ph b">Actions</strong> tab shows you details about the actions that make up the coordinator.<a name="topic_9_6_2__ul_nld_3nt_4j"><!-- --></a><ul class="ul" id="topic_9_6_2__ul_nld_3nt_4j">
|
|
|
+
|
|
|
+ <li class="li">Click the <strong class="ph b">Id</strong> link to see additional details about the
|
|
|
+ action.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click the <strong class="ph b">External Id</strong> link to view the job in the Job
|
|
|
+ Browser.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+ </li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">The <strong class="ph b">Configuration</strong> tab shows selected job configuration settings.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">The <strong class="ph b">Logs</strong> tab shows log output generated by the coordinator.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">The <strong class="ph b">Definition</strong> tab shows the Oozie coordinator definition, as it
|
|
|
+ appears in the <samp class="ph codeph">coordinator.xml</samp> file (also linked under the
|
|
|
+ <samp class="ph codeph">oozie.coord.application.path</samp> property in the
|
|
|
+ <strong class="ph b">Configuration</strong> tab).</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="topic concept nested2" id="concept_h1s_rtp_wj"><a name="concept_h1s_rtp_wj"><!-- --></a>
|
|
|
+ <h3 class="title topictitle3">Bundles</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+ <p class="p">Click the <strong class="ph b">Bundles</strong> tab to view the
|
|
|
+ running and completed bundle jobs for the filters you have specified. </p>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="topic concept nested2" id="concept_hvm_5vd_2k"><a name="concept_hvm_5vd_2k"><!-- --></a>
|
|
|
+ <h3 class="title topictitle3">Oozie</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+ <p class="p">The Oozie tab provides subtabs that give you access to Oozie instrumentation and
|
|
|
+ configuration settings.</p>
|
|
|
+
|
|
|
+ <div class="section" id="concept_hvm_5vd_2k__section_rbd_fwd_2k"><a name="concept_hvm_5vd_2k__section_rbd_fwd_2k"><!-- --></a><h4 class="title sectiontitle">Instrumentation</h4>
|
|
|
+
|
|
|
+ <p class="p">For information on the instrumentation metrics supported by Oozie, see <a class="xref" href="http://oozie.apache.org/docs/3.3.0/AG_Monitoring.html" target="_blank">Oozie Monitoring</a>.</p>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="section" id="concept_hvm_5vd_2k__section_zlh_cwd_2k"><a name="concept_hvm_5vd_2k__section_zlh_cwd_2k"><!-- --></a><h4 class="title sectiontitle">Configuration</h4>
|
|
|
+
|
|
|
+ <p class="p">For information on the configuration properties supported by Oozie, see <a class="xref" href="http://oozie.apache.org/docs/3.3.0/AG_Install.html#Oozie_Configuration" target="_blank">Oozie Configuration</a>.</p>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested1" xml:lang="en-US" lang="en-US" id="topic_9_7"><a name="topic_9_7"><!-- --></a>
|
|
|
+
|
|
|
+ <h2 class="title topictitle2">Workflow Manager
|
|
|
+ </h2>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p">In Workflow Manager you create Oozie workflows and submit them for
|
|
|
+ execution. </p>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ Click the <strong class="ph b">Workflows</strong> tab to open the Workflow Manager.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ Each row shows a workflow: its name, description, timestamp of its last modification. It also shows:
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Steps</strong> - the number of steps in the
|
|
|
+ workflow execution path. This is the number of execution steps between the start and end
|
|
|
+ of the workflow. This will not necessarily be the same as the number of actions in the
|
|
|
+ workflow, if there are control flow nodes in the control path.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Status</strong> - who can run the
|
|
|
+ workflow. <strong class="ph b">shared</strong> means users other than the owner can
|
|
|
+ access the workflow. <strong class="ph b">personal</strong> means only the owner can
|
|
|
+ modify or submit the workflow. The default is personal.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Owner</strong> - the user that created the
|
|
|
+ workflow.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ In Workflow Editor you edit workflows that include MapReduce, Streaming, Java, Pig, Hive, Sqoop, Shell, Ssh,
|
|
|
+ DistCp, Fs, Email, Sub-workflow, and Generic actions. You can configure these actions in the Workflow Editor, or
|
|
|
+ you can import job designs from Job Designer to be used as actions in your workflow. For information about
|
|
|
+ defining workflows, see the
|
|
|
+ <a class="xref" href="http://archive.cloudera.com/cdh4/cdh/4/oozie/WorkflowFunctionalSpec.html" target="_blank">Workflow
|
|
|
+ Specification</a>.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_2"><a name="topic_9_7_2"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Opening a Workflow</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">To open a workflow, in Workflow Manager, click the workflow. Proceed
|
|
|
+ with <a class="xref" href="#topic_9_7_7">Editing a Workflow</a>.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_3"><a name="topic_9_7_3"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Creating a Workflow</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">Click the <strong class="ph b">Create</strong> button at the top right.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">In the Name field, type a name.</li>
|
|
|
+
|
|
|
+ <li class="li">Check the <span class="ph uicontrol">Is shared</span> checkbox to allow all users to access the
|
|
|
+ workflow.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">advanced</strong> to specify the
|
|
|
+ deployment directory or a job.xml file.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">Save</strong>. The Workflow Editor opens. Proceed with <a class="xref" href="#topic_9_7_7">Editing a Workflow</a>.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_4"><a name="topic_9_7_4"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Importing a Workflow</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">Click the <strong class="ph b">Import</strong> button at the top right.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">In the Name field, type a name.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">In the <strong class="ph b">Local workflow.xml file</strong> field, click <strong class="ph b">Choose File</strong> and
|
|
|
+ select a workflow file.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">advanced</strong> to specify whether the workflow is shared, the
|
|
|
+ deployment directory, or a job.xml file.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">Save</strong>. The Workflow Editor opens. Proceed with <a class="xref" href="#topic_9_7_7">Editing a Workflow</a>.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_5"><a name="topic_9_7_5"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Submitting a Workflow</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">To submit a workflow for execution, do one of the following:
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li">In the Workflow Manager, click the radio button next to the workflow, and
|
|
|
+ click the <strong class="ph b">Submit</strong> button.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">In the Workflow Editor, click the <strong class="ph b">Submit</strong> button.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+<p class="p">The workflow job is submitted and the Dashboard displays the workflow job.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+<p class="p">To view the output of the job, click
|
|
|
+
|
|
|
+ <img class="image" src="/static/art/help/log.png"/>
|
|
|
+
|
|
|
+ <strong class="ph b">View the logs</strong>.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="section"><h4 class="title sectiontitle">Suspending a Running Job</h4>
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p"> In the pane on the left, click the <strong class="ph b">Suspend</strong> button.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">Verify that you want to suspend the job.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="section"><h4 class="title sectiontitle">Resuming a Suspended Job</h4>
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p"> In the pane on the left, click the <strong class="ph b">Resume</strong> button.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">Verify that you want to resume the job.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="section"><h4 class="title sectiontitle">Rerunning a Workflow</h4>
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p"> In the pane on the left, click the <strong class="ph b">Rerun</strong> button.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">Check the checkboxes next to the actions to rerun.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Specify required variables.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">Submit</strong>.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_6"><a name="topic_9_7_6"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Scheduling a Workflow</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">To schedule a workflow for recurring execution, do one of the following:
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li">In the Workflow Manager, check the checkbox next to the workflow
|
|
|
+ and click the <strong class="ph b">Schedule</strong> button.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">In the Workflow Editor, click the <strong class="ph b">Schedule</strong> button.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p" id="topic_9_7_6__p_102"><a name="topic_9_7_6__p_102"><!-- --></a>
|
|
|
+ A coordinator is created and opened in the Coordinator Editor. Proceed
|
|
|
+ with <a class="xref" href="#topic_9_8_4">Editing a Coordinator</a>.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_7"><a name="topic_9_7_7"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Editing a Workflow</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">In the Workflow Editor you can easily perform operations on Oozie action and control nodes.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="section"><h4 class="title sectiontitle">Action Nodes</h4>
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p"> The Workflow Editor supports dragging and dropping action nodes. As you move the action over other actions
|
|
|
+ and forks, highlights indicate active areas. If there are actions in the workflow, the active areas are the
|
|
|
+ actions themselves and the areas above and below the actions. If you drop an action on an existing action, a
|
|
|
+ fork and join is added to the workflow.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li">Add actions to the workflow by clicking an action <a name="topic_9_7_7__image_kpj_dnt_4j"><!-- --></a><img class="image" id="topic_9_7_7__image_kpj_dnt_4j" src="/static/art/help/action.png"/> button and drop the action on the workflow. The Edit Node
|
|
|
+ screen displays. <a name="topic_9_7_7__ol_l3q_dnt_4j"><!-- --></a><ol class="ol" id="topic_9_7_7__ol_l3q_dnt_4j">
|
|
|
+ <li class="li">Set the action properties and click <strong class="ph b">Done</strong>. Each action in a workflow must have a
|
|
|
+ unique name.</li>
|
|
|
+
|
|
|
+ </ol>
|
|
|
+</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li">Copy an action by clicking the <img class="image" src="/static/art/help/copy.png"/>
|
|
|
+ <strong class="ph b">Copy</strong> button.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ <a name="topic_9_7_7__ol_bjq_r55_yj"><!-- --></a><ol class="ol" id="topic_9_7_7__ol_bjq_r55_yj">
|
|
|
+ <li class="li">The action is opened in the Edit Node screen.</li>
|
|
|
+
|
|
|
+ <li class="li">Edit the action properties and click <strong class="ph b">Done</strong>. The action is added to the end of the
|
|
|
+ workflow.</li>
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li">Delete an action by clicking the <img class="image" src="/static/art/help/trash.png"/> button.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Edit an action by clicking the <img class="image" src="/static/art/help/edit.png"/> button.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Change the position of an action by left-clicking and dragging an action
|
|
|
+ to a new location.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="section"><h4 class="title sectiontitle">Control Nodes</h4>
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li">Create a fork and join by dropping an action on top of another
|
|
|
+ action.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Remove a fork and join by dragging a forked action and dropping it above
|
|
|
+ the fork.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Convert a fork to a decision by clicking the <img class="image" src="/static/art/help/convert.png"/>
|
|
|
+ button.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">To edit a decision: <a name="topic_9_7_7__ol_dcc_fnt_4j"><!-- --></a><ol class="ol" id="topic_9_7_7__ol_dcc_fnt_4j">
|
|
|
+ <li class="li">Click the <a name="topic_9_7_7__image_lcc_fnt_4j"><!-- --></a><img class="image" id="topic_9_7_7__image_lcc_fnt_4j" src="/static/art/help/edit.png"/> button.</li>
|
|
|
+
|
|
|
+ <li class="li">Fill in the predicates that determine which action to
|
|
|
+ perform and select the default action from the drop-down list.</li>
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">Done</strong>.</li>
|
|
|
+
|
|
|
+ </ol>
|
|
|
+</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_8"><a name="topic_9_7_8"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Uploading Workflow Files</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">In the Workflow Editor, click the <strong class="ph b">Upload</strong>
|
|
|
+ button. </p>
|
|
|
+
|
|
|
+ <p class="p">The workspace of the workflow is opened in the File Browser
|
|
|
+ application. Follow the procedure in <a class="xref" href="filebrowser.html#topic_6_3_4">Uploading Files</a> to upload the files. You must put JAR files in a
|
|
|
+ <span class="ph filepath">lib</span> directory in the
|
|
|
+ workspace.</p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_9"><a name="topic_9_7_9"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Editing Workflow Properties</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">In the Workflow Editor, click the link under the Name or Description fields
|
|
|
+ in the left pane.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">To share the workflow with all users, check the <strong class="ph b">Is shared</strong> checkbox.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">To set advanced execution options, click <strong class="ph b">advanced</strong> and edit the
|
|
|
+ deployment directory, add parameters and job properties, or specify a
|
|
|
+ job.xml file.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">Save</strong>.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_7_10"><a name="topic_9_7_10"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Displaying the History of a Workflow</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+ <li class="li">Click the <strong class="ph b">Dashboard</strong> tab.</li>
|
|
|
+
|
|
|
+ <li class="li">Click the <strong class="ph b">Workflows</strong> tab. </li>
|
|
|
+
|
|
|
+ <li class="li">Click a workflow.</li>
|
|
|
+
|
|
|
+ <li class="li">Click the <strong class="ph b">Actions</strong> tab.</li>
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested1" xml:lang="en-US" lang="en-US" id="topic_9_8"><a name="topic_9_8"><!-- --></a>
|
|
|
+
|
|
|
+ <h2 class="title topictitle2">Coordinator Manager
|
|
|
+ </h2>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ In Coordinator Manager you create Oozie coordinator applications and submit them for execution.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ Click the <strong class="ph b">Coordinators</strong> tab to open the Coordinator Manager.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ Each row shows a coordinator: its name, description, timestamp of its last modification. It also shows:
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ul class="ul">
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Workflow</strong> - the workflow that will
|
|
|
+ be run by the coordinator.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Frequency</strong> - how often the workflow
|
|
|
+ referenced by the coordinator will be run.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Status</strong> - who can run the
|
|
|
+ coordinator. <strong class="ph b">shared</strong> means users other than the owner can
|
|
|
+ access the workflow. <strong class="ph b">personal</strong> means only the owner can
|
|
|
+ modify or submit the workflow. The default is personal.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li"><strong class="ph b">Owner</strong> - the user that created the
|
|
|
+ coordinator.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ul>
|
|
|
+
|
|
|
+
|
|
|
+ <p class="p">
|
|
|
+ In Coordinator Editor, you edit coordinators and the datasets required by the coordinators. For information
|
|
|
+ about defining coordinators and datasets, see the
|
|
|
+ <a class="xref" href="http://archive.cloudera.com/cdh4/cdh/4/oozie/CoordinatorFunctionalSpec.html" target="_blank">Coordinator
|
|
|
+ Specification</a>.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_8_1"><a name="topic_9_8_1"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Opening a Coordinator</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">To open a coordinator, in Coordinator Manager, click the coordinator. Proceed with
|
|
|
+ <a class="xref" href="#topic_9_8_4">Editing a Coordinator</a>.
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_8_2"><a name="topic_9_8_2"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Creating a Coordinator</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">To create a coordinator, in Coordinator Manager:
|
|
|
+ </p>
|
|
|
+
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">Click the <strong class="ph b">Create</strong> button at the top right. The Coordinator wizard
|
|
|
+ opens. Proceed with <a class="xref" href="#topic_9_8_4">Editing a
|
|
|
+ Coordinator</a>.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_8_3"><a name="topic_9_8_3"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Submitting a Coordinator</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <p class="p" id="topic_9_8_3__p_110"><a name="topic_9_8_3__p_110"><!-- --></a> To submit a coordinator for execution, check the checkbox
|
|
|
+ next to the coordinator and click the <strong class="ph b">Submit</strong> button. </p>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_8_4"><a name="topic_9_8_4"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Editing a Coordinator</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+<p class="p">In the Coordinator Editor you specify coordinator properties and the datasets
|
|
|
+ on which the workflow scheduled by the coordinator will operate by stepping through
|
|
|
+ screens in a wizard. <span class="ph" id="topic_9_8_4__wizard"><a name="topic_9_8_4__wizard"><!-- --></a>You can also advance to particular steps and revisit
|
|
|
+ steps by clicking the Step "tabs" above the screens. The following instructions walk you
|
|
|
+ through the wizard. </span></p>
|
|
|
+
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">Type a name, select the workflow, check the <strong class="ph b">Is shared
|
|
|
+ checkbox</strong> to share the job, and click <strong class="ph b">Next</strong>. If
|
|
|
+ the Coordinator Editor was opened after scheduling a workflow, the workflow will be
|
|
|
+ set.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Select how many times the coordinator will run for each specified
|
|
|
+ unit, the start and end times of the coordinator, the timezone of the start and end
|
|
|
+ times, and click <strong class="ph b">Next</strong>. <span class="ph">Times must be expressed as
|
|
|
+ UTC times. For example, to run at 10 pm PST, specify a start time of 6 am UTC of the
|
|
|
+ following day (+8 hours) and set the Timezone field to America/Los_Angeles.</span></li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">Add</strong> to select an input dataset and click <strong class="ph b">Next</strong>. If no
|
|
|
+ datasets exist, follow the procedure in <a class="xref" href="#topic_9_8_5">Creating a Dataset</a>.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Click <strong class="ph b">Add</strong> to select an output dataset. Click <strong class="ph b">Save coordinator</strong>
|
|
|
+ or click <strong class="ph b">Next</strong> to specify advanced settings.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">To share the coordinator with all users, check the <strong class="ph b">Is</strong><strong class="ph b"> shared</strong>
|
|
|
+ checkbox.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li">Fill in parameters to pass to Oozie, properties that determine how long a
|
|
|
+ coordinator will wait before timing out, how many coordinators can run and
|
|
|
+ wait concurrently, and the coordinator execution policy.</li>
|
|
|
+
|
|
|
+
|
|
|
+ <li class="li" id="topic_9_8_4__li_120"><a name="topic_9_8_4__li_120"><!-- --></a>Click <strong class="ph b">Save coordinator</strong>.</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
+
|
|
|
+
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_8_5"><a name="topic_9_8_5"><!-- --></a>
|
|
|
+
|
|
|
+ <h3 class="title topictitle3">Creating a Dataset</h3>
|
|
|
+
|
|
|
+ <div class="body conbody">
|
|
|
+
|
|
|
+ <ol class="ol">
|
|
|
+
|
|
|
+ <li class="li">In the Coordinator Editor, do one of the following: <a name="topic_9_8_5__ul_ynh_gnt_4j"><!-- --></a><ul class="ul" id="topic_9_8_5__ul_ynh_gnt_4j">
|
|
|
+ <li class="li">Click <strong class="ph b">here</strong> in the Inputs or
|
|
|
+ Outputs pane at the top of the editor.</li>
|
|
|
+
|
|
|
+ <li class="li">In the pane at the left, click the <strong class="ph b">Create new</strong> link. Proceed with <a class="xref" href="#topic_9_8_7">Editing a
|
|
|
+ Dataset</a>.</li>
|
|
|
+
|
|
|
+ </ul>
|
|
|
+</li>
|
|
|
+
|
|
|
+
|
|
|
+ </ol>
|
|
|
+
|
|
|
+
|
|
|
+ </div>
|
|
|
|
|
|
-<p>Oozie Dashboard shows a summary of the running and completed workflow and coordinator jobs.</p>
|
|
|
|
|
|
-<p>You can view jobs for a period up to the last 30 days.</p>
|
|
|
+ </div>
|
|
|
|
|
|
-<p>You can filter the list by date (1, 7, 15, or 30 days) or status (Succeeded, Running, or Killed). The date and status buttons are toggles.</p>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-Workflows"></a>Workflows</h2>
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_8_6"><a name="topic_9_8_6"><!-- --></a>
|
|
|
|
|
|
-<p>Click the <b>Workflows</b> tab to view the running and completed workflow jobs for the filters you have specified.</p>
|
|
|
+ <h3 class="title topictitle3">Displaying Datasets</h3>
|
|
|
|
|
|
-<p>Click a workflow row in the Running or Completed table to view detailed information about that workflow job.</p>
|
|
|
+ <div class="body conbody">
|
|
|
|
|
|
-<p>For the selected job, the following information is available.</p>
|
|
|
+ <ol class="ol">
|
|
|
|
|
|
-<ul>
|
|
|
- <li>The <b>Graph</b> tab shows the workflow DAG.</li>
|
|
|
- <li>The <b>Actions</b> tab shows you details about the actions that make up the workflow.
|
|
|
- <ul>
|
|
|
- <li>Click the <b>Id</b> link to see additional details about the action.</li>
|
|
|
- <li>Click the <b>External Id</b> link to view the job in the Job Browser.</li>
|
|
|
- </ul>
|
|
|
- </li>
|
|
|
- <li>The <b>Details</b> tab shows job statistics including start and end times, and provides a link to the workflow definition in the File Browser.</li>
|
|
|
- <li>The <b>Configuration</b> tab shows selected job configuration settings.</li>
|
|
|
- <li>The <b>Logs</b> tab shows log output generated by the workflow job.</li>
|
|
|
- <li>The <b>Definition</b> tab shows the Oozie workflow definition, as it appears in the <tt>workflow.xml</tt> file (also linked under the application path properties in the <b>Details</b> tab and the <b>Configuration</b> tab).</li>
|
|
|
-</ul>
|
|
|
+ <li class="li">In the Coordinator Editor, click <strong class="ph b">Show existing</strong> in pane at the
|
|
|
+ left.</li>
|
|
|
|
|
|
|
|
|
+ <li class="li" id="topic_9_8_6__li_121"><a name="topic_9_8_6__li_121"><!-- --></a>To edit a dataset, click the dataset name in the Existing
|
|
|
+ datasets table. Proceed with <a class="xref" href="#topic_9_8_7">Editing
|
|
|
+ a Dataset</a>.</li>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-Coordinators"></a>Coordinators</h2>
|
|
|
|
|
|
-<p>Click the <b>Coordinators</b> tab to view the running and completed coordinator jobs for the filters you have specified.</p>
|
|
|
+ </ol>
|
|
|
|
|
|
-<p>For the selected job, the following information is available.</p>
|
|
|
-<ul>
|
|
|
- <li>The <b>Calendar</b> tab shows the timestamp of the job. Click the timestamp to open the workflow DAG. </li>
|
|
|
- <li>The <b>Actions</b> tab shows you details about the actions that make up the coordinator.
|
|
|
- <ul>
|
|
|
- <li>Click the <b>Id</b> link to see additional details about the action.</li>
|
|
|
- <li>Click the <b>External Id</b> link to view the job in the Job Browser.</li>
|
|
|
- </ul>
|
|
|
- </li>
|
|
|
- <li>The <b>Configuration</b> tab shows selected job configuration settings.</li>
|
|
|
- <li>The <b>Logs</b> tab shows log output generated by the coordinator.</li>
|
|
|
- <li>The <b>Definition</b> tab shows the Oozie coordinator definition, as it appears in the <tt>coordinator.xml</tt> file (also linked under the oozie.coord.application.path property in the <b>Configuration</b> tab).</li>
|
|
|
-</ul>
|
|
|
|
|
|
+ </div>
|
|
|
|
|
|
-<h1><a name="OozieEditorandDashboard-WorkflowManager"></a>Workflow Manager</h1>
|
|
|
|
|
|
-<p>In Workflow Manager you create Oozie workflows and submit them for execution.</p>
|
|
|
+ </div>
|
|
|
|
|
|
-<p>Click the <b>Workflows</b> tab to open the Workflow Manager.</p>
|
|
|
|
|
|
-<p>Each row shows a workflow: its name, description, timestamp of its last modification. It also shows:</p>
|
|
|
-<ul>
|
|
|
- <li><b>Steps</b>: the number of steps in the workflow execution path. This is the number of execution steps between the start and end of the workflow. This will not necessarily be the same as the number of actions in the workflow, if there are control flow nodes in the control path.</li>
|
|
|
- <li><b>Status</b>: who can run the workflow. <b>shared</b> means users other than the owner can access the workflow. <b>personal</b> means only the owner can modify or submit the workflow. The default is personal.</li>
|
|
|
- <li><b>Owner</b>: the user that created the workflow.</li>
|
|
|
-</ul>
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_8_7"><a name="topic_9_8_7"><!-- --></a>
|
|
|
|
|
|
+ <h3 class="title topictitle3">Editing a Dataset</h3>
|
|
|
|
|
|
-<p>In Workflow Editor you edit workflows that include MapReduce, Streaming, Java, Pig, Hive, Sqoop, Shell, Ssh, DistCp, Fs, Email, Sub-workflow, and Generic actions. You can configure these actions in the Workflow Editor, or you can import job designs from Job Designer to be used as actions in your workflow. For information about defining workflows, see the <a href="http://archive.cloudera.com/cdh4/cdh/4/oozie/WorkflowFunctionalSpec.html">Workflow Specification</a>.</p>
|
|
|
+ <div class="body conbody">
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-InstallingtheSampleWorkflows"></a>Installing the Sample Workflows</h2>
|
|
|
+ <ol class="ol">
|
|
|
|
|
|
-<ol>
|
|
|
- <li>Click the <b>Setup Examples</b> button at the top right.</li>
|
|
|
-</ol>
|
|
|
+ <li class="li">Type a name for the dataset.</li>
|
|
|
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-OpeningaWorkflow"></a>Opening a Workflow</h2>
|
|
|
+ <li class="li">In the Start and Frequency fields, specify when and how often the dataset
|
|
|
+ will be available.</li>
|
|
|
|
|
|
-<p>To open a workflow, in Workflow Manager, click the workflow. Proceed with <a href="#OozieEditorandDashboard-EditingaWorkflow">Editing a Workflow</a>.</p>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-CreatingaWorkflow"></a>Creating a Workflow</h2>
|
|
|
+ <li class="li">In the URI field, specify a URI template for the location of the
|
|
|
+ dataset. To construct URIs and URI paths containing dates and timestamps, you can
|
|
|
+ specify the variables <samp class="ph codeph">${YEAR}</samp><samp class="ph codeph">,$</samp><samp class="ph codeph">{MONTH},${DAY},${HOUR},${MINUTE}</samp>. For example:<samp class="ph codeph">
|
|
|
+ hdfs://foo:9000/usr/app/stats/${YEAR}/${MONTH}/data</samp>.</li>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>Click the <b>Create</b> button at the top right.</li>
|
|
|
- <li>In the Name field, type a name.</li>
|
|
|
- <li>Click <b>advanced</b> to specify whether the workflow is shared, the deployment directory, or a job.xml file.</li>
|
|
|
- <li>Click <b>Save</b>. The Workflow Editor opens. Proceed with <a href="#OozieEditorandDashboard-EditingaWorkflow">Editing a Workflow</a>.</li>
|
|
|
-</ol>
|
|
|
|
|
|
+ <li class="li">In the Instance field, click a button to choose a default, single, or range
|
|
|
+ of data instances. For example, if frequency==DAY, a window of the last
|
|
|
+ rolling 5 days (not including today) would be expressed as start: -5 and
|
|
|
+ end: -1. Check the advanced checkbox to display a field where you can
|
|
|
+ specify a coordinator <a class="xref" href="http://archive.cloudera.com/cdh4/cdh/4/oozie/CoordinatorFunctionalSpec.html" target="_blank">EL function</a>.</li>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-ImportingaWorkflow"></a>Importing a Workflow</h2>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>Click the <b>Import</b> button at the top right.</li>
|
|
|
- <li>In the Name field, type a name.</li>
|
|
|
- <li>In the <b>Local workflow.xml file</b> field, click <b>Choose File</b> and select a workflow file.</li>
|
|
|
- <li>Click <b>advanced</b> to specify whether the workflow is shared, the deployment directory, or a job.xml file.</li>
|
|
|
- <li>Click <b>Save</b>. The Workflow Editor opens. Proceed with <a href="#OozieEditorandDashboard-EditingaWorkflow">Editing a Workflow</a>.</li>
|
|
|
-</ol>
|
|
|
+ <li class="li">Specify the timezone of the start date.</li>
|
|
|
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-SubmittingaWorkflow"></a>Submitting a Workflow</h2>
|
|
|
+ <li class="li">In the Done flag field, specify the flag that identifies when input datasets
|
|
|
+ are no longer ready.</li>
|
|
|
|
|
|
-<p>To submit a workflow for execution, do one of the following:</p>
|
|
|
|
|
|
-<ul>
|
|
|
- <li>In the Workflow Manager, click the radio button next to the workflow, and click the <b>Submit</b> button.</li>
|
|
|
- <li>In the Workflow Editor, click the <b>Submit</b> button.</li>
|
|
|
-</ul>
|
|
|
+ </ol>
|
|
|
|
|
|
|
|
|
-<p>The workflow job is submitted and the Dashboard displays the workflow job.</p>
|
|
|
+ </div>
|
|
|
|
|
|
-<p>To view the output of the job, click <span class="image-wrap" style=""><img src="/jobsub/static/help/images/23888324.png" style="border: 0px solid black"/></span> <b>View the logs</b>.</p>
|
|
|
|
|
|
-<h3><a name="OozieEditorandDashboard-SuspendingaRunningJob"></a>Suspending a Running Job</h3>
|
|
|
+ </div>
|
|
|
|
|
|
-<p>In the pane on the left, click the <b>Suspend</b> button.</p>
|
|
|
-<ol>
|
|
|
- <li>Verify that you want to suspend the job.</li>
|
|
|
-</ol>
|
|
|
|
|
|
+ <div class="topic concept nested2" xml:lang="en-US" lang="en-US" id="topic_9_8_8"><a name="topic_9_8_8"><!-- --></a>
|
|
|
|
|
|
-<h3><a name="OozieEditorandDashboard-ResumingaSuspendedJob"></a>Resuming a Suspended Job</h3>
|
|
|
+ <h3 class="title topictitle3">Displaying the History of a Coordinator</h3>
|
|
|
|
|
|
-<p>In the pane on the left, click the <b>Resume</b> button.</p>
|
|
|
-<ol>
|
|
|
- <li>Verify that you want to resume the job.</li>
|
|
|
-</ol>
|
|
|
+ <div class="body conbody">
|
|
|
|
|
|
+ <ol class="ol">
|
|
|
+ <li class="li">Click the <strong class="ph b">Dashboard</strong> tab.</li>
|
|
|
|
|
|
-<h3><a name="OozieEditorandDashboard-RerunningaWorkflow"></a>Rerunning a Workflow</h3>
|
|
|
+ <li class="li">Click the <strong class="ph b">Coordinators</strong> tab. </li>
|
|
|
|
|
|
-<p>In the pane on the left, click the <b>Rerun</b> button.</p>
|
|
|
-<ol>
|
|
|
- <li>Check the checkboxes next to the actions to rerun.</li>
|
|
|
- <li>Specify required variables.</li>
|
|
|
- <li>Click <b>Submit</b>.</li>
|
|
|
-</ol>
|
|
|
+ <li class="li">Click a coordinator.</li>
|
|
|
|
|
|
+ <li class="li">Click the <strong class="ph b">Actions</strong> tab.</li>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-SchedulingaWorkflow"></a>Scheduling a Workflow</h2>
|
|
|
+ </ol>
|
|
|
|
|
|
-<p>To schedule a workflow for recurring execution, do one of the following:</p>
|
|
|
|
|
|
-<ul>
|
|
|
- <li>In the Workflow Manager, click the radio button next to the workflow and click the <b>Schedule</b> button.</li>
|
|
|
- <li>In the Workflow Editor, click the <b>Schedule</b> button.</li>
|
|
|
-</ul>
|
|
|
+ </div>
|
|
|
|
|
|
|
|
|
-<p>A coordinator is created and opened in the Coordinator Editor. Proceed with <a href="#OozieEditorandDashboard-EditingaCoordinator">Editing a Coordinator</a>.</p>
|
|
|
+ </div>
|
|
|
|
|
|
-<p><a name="OozieEditorandDashboard-EditingaWorkflow"></a></p>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-EditingaWorkflow"></a>Editing a Workflow</h2>
|
|
|
+ </div>
|
|
|
|
|
|
-<p>In the Workflow Editor you can easily perform operations on Oozie action and control nodes.</p>
|
|
|
+ <div class="topic concept nested1" id="concept_crd_ttp_wj"><a name="concept_crd_ttp_wj"><!-- --></a>
|
|
|
+ <h2 class="title topictitle2">Bundle Manager</h2>
|
|
|
|
|
|
-<h3><a name="OozieEditorandDashboard-ActionNodes"></a>Action Nodes</h3>
|
|
|
+ <div class="body conbody">
|
|
|
+ <p class="p">In Bundle Manager you create Oozie bundle applications and submit them
|
|
|
+ for execution. </p>
|
|
|
|
|
|
-<p>The Workflow Editor supports dragging and dropping action nodes. As you move the action over other actions and forks, highlights indicate active areas. If there are actions in the workflow, the active areas are the actions themselves and the areas above and below the actions. If you drop an action on an existing action, a fork and join is added to the workflow.</p>
|
|
|
+ <p class="p">Click the <strong class="ph b">Bundle</strong> tab to open the
|
|
|
+ Bundle Manager. </p>
|
|
|
|
|
|
-<ul>
|
|
|
- <li>Add actions to the workflow by doing one of the following:
|
|
|
- <ul>
|
|
|
- <li>Click an action (<span class="image-wrap" style=""><img src="/jobsub/static/help/images/23888498.png" style="border: 0px solid black"/></span>) button and drop the action on the workflow. The Edit Node screen displays.
|
|
|
- <ol>
|
|
|
- <li>Set the action properties and click <b>Done</b>. Each action in a workflow must have a unique name.</li>
|
|
|
- </ol>
|
|
|
- </li>
|
|
|
- <li>Click the <b>Import action</b> link to import an existing job design. The Import Action screen displays.
|
|
|
- <ol>
|
|
|
- <li>Click a radio button next to a job design and click <b>Import</b>. The action is added to the end of the workflow.</li>
|
|
|
- </ol>
|
|
|
- </li>
|
|
|
- </ul>
|
|
|
- </li>
|
|
|
- <li>Clone an action by clicking the <span class="image-wrap" style=""><img src="/jobsub/static/help/images/23888163.png" style="border: 0px solid black"/></span> button.
|
|
|
- <ol>
|
|
|
- <li>The action is opened in the Edit Node screen.</li>
|
|
|
- <li>Edit the action properties and click <b>Done</b>. The action is added to the end of the workflow.</li>
|
|
|
- </ol>
|
|
|
- </li>
|
|
|
- <li>Delete an action by clicking the <span class="image-wrap" style=""><img src="/jobsub/static/help/images/23888458.png" style="border: 0px solid black"/></span> button.</li>
|
|
|
- <li>Edit an action by clicking the <span class="image-wrap" style=""><img src="/jobsub/static/help/images/23888457.png" style="border: 0px solid black"/></span> button.</li>
|
|
|
- <li>Change the position of an action by left-clicking and dragging an action to a new location.</li>
|
|
|
-</ul>
|
|
|
+ <p class="p">Each row shows a bundle: its name, description, timestamp of its last
|
|
|
+ modification. It also shows: </p>
|
|
|
|
|
|
+ <a name="concept_crd_ttp_wj__ul_skt_5kj_2k"><!-- --></a><ul class="ul" id="concept_crd_ttp_wj__ul_skt_5kj_2k">
|
|
|
+ <li class="li"><strong class="ph b">Coordinators</strong> - the coordinators
|
|
|
+ that will be run by the bundle.</li>
|
|
|
|
|
|
-<h3><a name="OozieEditorandDashboard-ControlNodes"></a>Control Nodes</h3>
|
|
|
+ <li class="li"><strong class="ph b">Kick off</strong> - the UTC time when the
|
|
|
+ coordinators referenced by the bundle will be started. </li>
|
|
|
|
|
|
-<ul>
|
|
|
- <li>Create a fork and join by dropping an action on top of another action.</li>
|
|
|
- <li>Remove a fork and join by dragging a forked action and dropping it above the fork.</li>
|
|
|
- <li>Convert a fork to a decision by clicking the <span class="image-wrap" style=""><img src="/jobsub/static/help/images/23888456.png" style="border: 0px solid black"/></span> button.</li>
|
|
|
- <li>To edit a decision:
|
|
|
- <ol>
|
|
|
- <li>Click the <span class="image-wrap" style=""><img src="/jobsub/static/help/images/23888457.png" style="border: 0px solid black"/></span> button.</li>
|
|
|
- <li>Fill in the predicates that determines which action to perform and select the default action from the drop-down list.</li>
|
|
|
- <li>Click <b>Done</b>.</li>
|
|
|
- </ol>
|
|
|
- </li>
|
|
|
-</ul>
|
|
|
+ <li class="li"><strong class="ph b">Status</strong> - who can run the bundle.
|
|
|
+ <strong class="ph b">shared</strong> means users other than the owner can access the
|
|
|
+ workflow. <strong class="ph b">personal</strong> means only the owner can modify or
|
|
|
+ submit the workflow. The default is personal.</li>
|
|
|
|
|
|
+ <li class="li"><strong class="ph b">Owner</strong> - the user that created the
|
|
|
+ bundle.</li>
|
|
|
|
|
|
+ </ul>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-UploadingWorkflowFiles"></a>Uploading Workflow Files</h2>
|
|
|
+ <p class="p">For information about defining bundles, see the <a class="xref" href="http://archive.cloudera.com/cdh4/cdh/4/oozie/BundleFunctionalSpec.html" target="_blank"> Bundle
|
|
|
+ Specification</a>.</p>
|
|
|
|
|
|
-<p>In the Workflow Editor, click the <b>Upload</b> button.</p>
|
|
|
+ </div>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-EditingWorkflowProperties"></a>Editing Workflow Properties</h2>
|
|
|
+ <div class="topic concept nested2" id="concept_t5k_wqj_2k"><a name="concept_t5k_wqj_2k"><!-- --></a>
|
|
|
+ <h3 class="title topictitle3">Opening a Bundle</h3>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>In the Workflow Editor, click the link under the Name or Description fields in the left pane.</li>
|
|
|
- <li>To share the workflow with all users, check the <b>Is shared</b> checkbox.</li>
|
|
|
- <li>To set advanced execution options, click <b>advanced</b> and edit the deployment directory, add parameters and job properties, or specify a job.xml file.</li>
|
|
|
- <li>Click <b>Save</b>.</li>
|
|
|
-</ol>
|
|
|
+ <div class="body conbody">
|
|
|
+ <p class="p">To open a bundle, in Bundle Manager, click the bundle. Proceed with
|
|
|
+ <a class="xref" href="#concept_ur1_gmj_2k">Editing a Bundle</a>. </p>
|
|
|
|
|
|
+ </div>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-DisplayingtheHistoryofaWorkflow"></a>Displaying the History of a Workflow</h2>
|
|
|
+ </div>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>Do one of the following:
|
|
|
- <ul>
|
|
|
- <li>In the Workflow Editor, click <b>Show history</b> in the pane at the left. Click a job.</li>
|
|
|
- <li>In the Oozie Dashboard/Editor, click the <b>History</b> tab. Click a submission Id.</li>
|
|
|
- </ul>
|
|
|
- </li>
|
|
|
-</ol>
|
|
|
+ <div class="topic concept nested2" id="concept_rvt_gmj_2k"><a name="concept_rvt_gmj_2k"><!-- --></a>
|
|
|
+ <h3 class="title topictitle3">Creating a Bundle</h3>
|
|
|
|
|
|
+ <div class="body conbody">
|
|
|
+ <a name="concept_rvt_gmj_2k__ol_wgk_jmj_2k"><!-- --></a><ol class="ol" id="concept_rvt_gmj_2k__ol_wgk_jmj_2k">
|
|
|
+ <li class="li">Click the <strong class="ph b">Create</strong> button at the
|
|
|
+ top right.</li>
|
|
|
|
|
|
-<h1><a name="OozieEditorandDashboard-CoordinatorManager"></a>Coordinator Manager</h1>
|
|
|
+ <li class="li">In the Name field, type a name.</li>
|
|
|
|
|
|
-<p>In Coordinator Manager you create Oozie coordinator applications and submit them for execution. </p>
|
|
|
+ <li class="li">In the Kick off time field, choose a kick off time. </li>
|
|
|
|
|
|
-<p>Click the <b>Coordinators</b> tab to open the Coordinator Manager.</p>
|
|
|
+ <li class="li">Check the <span class="ph uicontrol">Is
|
|
|
+ shared</span> checkbox to allow all users to access the workflow.</li>
|
|
|
|
|
|
-<p>Each row shows a coordinator: its name, description, timestamp of its last modification. It also shows:</p>
|
|
|
-<ul>
|
|
|
- <li><b>Workflow</b>: the workflow that will be run by the coordinator.</li>
|
|
|
- <li><b>Frequency</b>: how often the workflow referenced by the coordinator will be run.</li>
|
|
|
- <li><b>Status</b>: who can run the coordinator. <b>shared</b> means users other than the owner can access the workflow. <b>personal</b> means only the owner can modify or submit the workflow. The default is personal.</li>
|
|
|
- <li><b>Owner</b>: the user that created the workflow.</li>
|
|
|
-</ul>
|
|
|
+ <li class="li">Click <strong class="ph b">Save</strong>. The Bundle Editor
|
|
|
+ opens. Proceed with <a class="xref" href="#concept_ur1_gmj_2k">Editing a Bundle</a>.</li>
|
|
|
|
|
|
+ </ol>
|
|
|
|
|
|
-<p>In Coordinator Editor, you edit coordinators and the datasets required by the coordinators. For information about defining coordinators and datasets, see the <a href="http://archive.cloudera.com/cdh4/cdh/4/oozie/CoordinatorFunctionalSpec.html">Coordinator Specification</a>.</p>
|
|
|
+ </div>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-OpeningaCoordinator"></a>Opening a Coordinator</h2>
|
|
|
+ </div>
|
|
|
|
|
|
-<p>To open a coordinator, in Coordinator Manager, click the coordinator. Proceed with <a href="#OozieEditorandDashboard-EditingaCoordinator">Editing a Coordinator</a>.</p>
|
|
|
+ <div class="topic concept nested2" id="concept_fcd_1rj_2k"><a name="concept_fcd_1rj_2k"><!-- --></a>
|
|
|
+ <h3 class="title topictitle3">Submitting a Bundle</h3>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-CreatingaCoordinator"></a>Creating a Coordinator</h2>
|
|
|
+ <div class="body conbody">
|
|
|
+ <p class="p">To submit a bundle for execution, check the checkbox next to the
|
|
|
+ bundle and click the <strong class="ph b">Submit</strong> button. </p>
|
|
|
|
|
|
-<p>To create a coordinator, in Coordinator Manager:</p>
|
|
|
-<ol>
|
|
|
- <li>Click the *Create button at the top right. The Coordinator wizard opens. Proceed with <a href="#OozieEditorandDashboard-EditingaCoordinator">Editing a Coordinator</a>.</li>
|
|
|
-</ol>
|
|
|
+ </div>
|
|
|
|
|
|
+ </div>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-SubmittingaCoordinator"></a>Submitting a Coordinator</h2>
|
|
|
+ <div class="topic concept nested2" id="concept_ur1_gmj_2k"><a name="concept_ur1_gmj_2k"><!-- --></a>
|
|
|
+ <h3 class="title topictitle3">Editing a Bundle</h3>
|
|
|
|
|
|
-<p>To submit a coordinator for execution, click the radio button next to the coordinator and click the <b>Submit</b> button.</p>
|
|
|
+ <div class="body conbody">
|
|
|
+ <p class="p">In the Bundle Editor, you specify properties by stepping through
|
|
|
+ screens in a wizard. <span class="ph">You can also advance to particular steps and revisit
|
|
|
+ steps by clicking the Step "tabs" above the screens. The following instructions walk you
|
|
|
+ through the wizard. </span>
|
|
|
+ </p>
|
|
|
|
|
|
-<p><a name="OozieEditorandDashboard-EditingaCoordinator"></a></p>
|
|
|
+ <a name="concept_ur1_gmj_2k__ol_evj_rmj_2k"><!-- --></a><ol class="ol" id="concept_ur1_gmj_2k__ol_evj_rmj_2k">
|
|
|
+ <li class="li">Click <strong class="ph b">Add</strong> to select a
|
|
|
+ coordinator that the bundle will kick off.</li>
|
|
|
|
|
|
+ <li class="li">Choose the kick off time. The time must be expressed as a UTC
|
|
|
+ time. For example, to run at 10 pm PST, specify a start time of 6 am UTC of the
|
|
|
+ following day (+8 hours).</li>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-EditingaCoordinator"></a>Editing a Coordinator</h2>
|
|
|
+ <li class="li">To share the bundle with all users, check the <strong class="ph b">Is shared</strong> checkbox.</li>
|
|
|
|
|
|
-<p>In the Coordinator Editor you specify coordinator properties and the datasets on which the workflow scheduled by the coordinator will operate by stepping through screens in a wizard. You can also advance to particular steps and revisit steps by clicking the Step "tabs" above the screens. The following instructions walk you through the coordinator wizard. </p>
|
|
|
+ <li class="li">Click <strong class="ph b">Next</strong> to specify advanced
|
|
|
+ settings or click <strong class="ph b">Save bundle</strong>.</li>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>Type a name, select the workflow, check the Is shared checkbox to share the job, and click <b>Next</b>. If the Coordinator Editor was opened after scheduling a workflow, the workflow will be set.</li>
|
|
|
- <li>Select how many times the communicator will run for each specified unit, the start and end times of the coordinator, the timezone of the start and end times, and click <b>Next</b>. The start and end times must be expressed as UTC times. For example, to run at 10 pm PST, specify a start time of 6 am UTC of the following day (+8 hours) and set the Timezone field to America/Los_Angeles.</li>
|
|
|
- <li>Click <b>Add</b> to select an input dataset and click <b>Next</b>. If no datasets exist, follow the procedure in <a href="#OozieEditorandDashboard-CreatingaDataset">Creating a Dataset</a>.</li>
|
|
|
- <li>Click <b>Add</b> to select an output dataset. Click <b>Save coordinator</b> or click <b>Next</b> to specify advanced settings.</li>
|
|
|
- <li>To share the coordinator with all users, check the <b>Is shared</b> checkbox.</li>
|
|
|
- <li>Fill in parameters to pass to Oozie, properties that determine how long a coordinator will wait before timing out, how many coordinators can run and wait concurrently, and the coordinator execution policy.</li>
|
|
|
- <li>Click <b>Save coordinator</b>.</li>
|
|
|
-</ol>
|
|
|
+ <li class="li">Fill in parameters to pass to Oozie.</li>
|
|
|
|
|
|
+ <li class="li">Click <strong class="ph b">Save bundle</strong>.</li>
|
|
|
|
|
|
+ </ol>
|
|
|
|
|
|
-<p><a name="OozieEditorandDashboard-CreatingaDataset"></a></p>
|
|
|
+ </div>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-CreatingaDataset"></a>Creating a Dataset</h2>
|
|
|
+ </div>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>In the Coordinator Editor, do one of the following:
|
|
|
- <ul>
|
|
|
- <li>Click <b>here</b> in the Inputs or Outputs pane at the top of the editor.</li>
|
|
|
- <li>In the pane at the left, click the <b>Create new</b> link. Proceed with <a href="#OozieEditorandDashboard-EditingaDataset">Editing a Dataset</a>.</li>
|
|
|
- </ul>
|
|
|
- </li>
|
|
|
-</ol>
|
|
|
+ </div>
|
|
|
|
|
|
+ <div class="topic concept nested1" id="concept_alh_gqj_2k"><a name="concept_alh_gqj_2k"><!-- --></a>
|
|
|
+ <h2 class="title topictitle2">Displaying the History of a Bundle</h2>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-DisplayingDatasets"></a>Displaying Datasets</h2>
|
|
|
+ <div class="body conbody">
|
|
|
+ <a name="concept_alh_gqj_2k__ol_rdg_hqj_2k"><!-- --></a><ol class="ol" id="concept_alh_gqj_2k__ol_rdg_hqj_2k">
|
|
|
+ <li class="li">Click the <strong class="ph b">Dashboard</strong> tab.</li>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>In the Coordinator Editor, click <b>Show existing</b> in pane at the left.</li>
|
|
|
- <li>To edit a dataset, click the dataset name in the Existing datasets table. Proceed with <a href="#OozieEditorandDashboard-EditingaDataset">Editing a Dataset</a>.</li>
|
|
|
-</ol>
|
|
|
+ <li class="li">Click the <strong class="ph b">Bundles</strong> tab. </li>
|
|
|
|
|
|
+ <li class="li">Click a bundle.</li>
|
|
|
|
|
|
-<p><a name="OozieEditorandDashboard-EditingaDataset"></a></p>
|
|
|
-<h2><a name="OozieEditorandDashboard-EditingaDataset"></a>Editing a Dataset</h2>
|
|
|
+ <li class="li">Click the <strong class="ph b">Actions</strong> tab.</li>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>Type a name for the dataset.</li>
|
|
|
- <li>In the Start and Frequency fields, specify when and how often the dataset will be available.</li>
|
|
|
- <li>In the URI field, specify a URI template for the location of the dataset. To construct URIs and URI paths containing dates and timestamps, you can specify the variables <tt>${YEAR},${MONTH},${DAY},${HOUR},${MINUTE</tt><tt>}</tt>. For example: <tt>hdfs://foo:9000/usr/app/stats/${YEAR}/${MONTH}/data</tt>.</li>
|
|
|
- <li>In the Instance field, click a button to choose a default, single, or range of data instances. For example, if frequency==DAY, a window of the last rolling 5 days (not including today) would be expressed as start: -5 and end: -1. Check the advanced checkbox to display a field where you can specify a coordinator <a href="http://archive.cloudera.com/cdh4/cdh/4/oozie/CoordinatorFunctionalSpec.html#a6.6._Parameterization_of_Dataset_Instances_in_Input_and_Output_Events">EL function</a>.</li>
|
|
|
- <li>Specify the timezone of the start date.</li>
|
|
|
- <li>In the Done flag field, specify the flag that identifies when input datasets are no longer ready.</li>
|
|
|
-</ol>
|
|
|
+ </ol>
|
|
|
|
|
|
+ </div>
|
|
|
|
|
|
-<h2><a name="OozieEditorandDashboard-DisplayingtheHistoryofaCoordinator"></a>Displaying the History of a Coordinator</h2>
|
|
|
+ </div>
|
|
|
|
|
|
-<ol>
|
|
|
- <li>Do one of the following:
|
|
|
- <ul>
|
|
|
- <li>In the Coordinator Editor, click <b>Show history</b> in the pane at the left. Click a job.</li>
|
|
|
- <li>In the Oozie Dashboard/Editor, click the <b>History</b> tab. Click a coordinator.</li>
|
|
|
- </ul>
|
|
|
- </li>
|
|
|
-</ol>
|
|
|
|
|
|
|
|
|
- <br/>
|
|
|
- </td>
|
|
|
- </tr>
|
|
|
- </table>
|
|
|
-
|
|
|
- </body>
|
|
|
-</html>
|
|
|
+</body>
|
|
|
+</html>
|