anchor.diff:  
   _The Celos UI_
   
  -=== Oozie
  +=== Oozie Overview
   
   Celos works as a frontend to the
   link:https://oozie.apache.org/[_Apache Oozie_] execution engine.
  
positive.code: zero-padded values from the slot's scheduled time.
  
  `year`, `month`, `day`, `hour`, `minute`, and `second` will also be
  set as Oozie properties, so they can be used in the workflow.xml.
  
  Additionally, Celos will set the Oozie property `celosWorkflowName` to
  a string like "my-workflow@2015-09-12T20:00Z", useful for display.
  
negative.code: 
  image::etc/images/oozie.png[Oozie workflow directory]
  
  Oozie requires a small XML file that describes what the job should do
  (in this case call a Java main with some arguments), and then runs it
  on a processing node in the cluster.  Artefacts in the `lib` directory
  are automatically placed on the classpath.  Arguments (such as
  `inputPath` and `outputPath` in the above example) can be passed to
  the job.
  
  Oozie XML files support
  link:https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html[many
  