[
https://issues.apache.org/jira/browse/OOZIE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1567:
---------------------------------
Attachment: OOZIE-1567.patch
The patch adds a {{-poll}} option that works when you use {{-start}} or
{{-run}} on a workflow. It does not work for Coordinators or Bundles; the idea
being we don't want users to poll the Oozie server with this for possibly days
or weeks or longer.
I set it to poll every 5 seconds; that might be too frequent though. Any
thoughts on a good interval?
While polling, it prints out {{Polling...}} and every interval, it prints
another period {{.}} until the job finishes and the final status gets printed
out. e.g. {{Polling........SUCCEEDED}}
I thought about having it print out the current action, but that would be
difficult without the server pushing that information to the client. I believe
the main use case for this feature is so that external tools can simply submit
a workflow and only return when it finishes, instead of having to handle the
polling themselves.
I'm not sure that this can be practically unit tested, but I did try it out
manually.
> Provide a wait tool in Oozie
> ----------------------------
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
> Issue Type: New Feature
> Components: core
> Affects Versions: 4.0.0
> Reporter: Viji
> Assignee: Robert Kanter
> Priority: Trivial
> Attachments: OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie
> workflow is successful or not, it is done by constantly pinging the oozie
> workflow status (that is, manual scripts need to be written). It would be
> good if Oozie provided a {{oozie wait -jobID <JOBID>}} or similar.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
