[
https://issues.apache.org/jira/browse/OOZIE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120379#comment-14120379
]
Robert Kanter commented on OOZIE-1567:
--------------------------------------
{quote}In CLI, you can take it in mins. For an automated application on top of
oozie, waiting for mins doesn't work. The java API can take the argument in
msecs.{quote}
That's a good compromise. I'll do that.
As for allowing -poll to be used as an action and an argument like -dryrun, I
don't think that will be as easy because when used as an action, it needs to
take an argument (the job id) but as an argument it has no arguments. Even if
we hack something to accept that, it's going to be confusing for the user. So
I'm inclined to just keep it as an action.
> 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, OOZIE-1567.patch, OOZIE-1567.patch,
> OOZIE-1567.patch, 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.3.4#6332)
