[
https://issues.apache.org/jira/browse/OOZIE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110075#comment-14110075
]
Robert Kanter commented on OOZIE-1567:
--------------------------------------
{quote}Why would the poll require -run or -start. I thought the command is:
oozie job -poll <job id>{quote}
I had originally envisioned that the user would do something like {{oozie job
-config job.properties -run -poll}} which would start the job and do the
polling. In hindsight, I think it will be simpler if we make it a separate
command like you suggest. i.e. you'd submit the job and then do {{oozie poll
<job_id>}}. A {{-timeout <seconds>}} argument is also a good idea. Maybe a
{{-interval <seconds>}} would also be useful. These and any other arguments we
want to add later, will be easier and clearer with poll being a separate
command.
I'll post a new patch when I've refactored that.
> 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)
