[
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
{quote}Do we need to specify option -id, the command can be just "oozie poll
<job_id>”?{quote}
I think this makes it a bit more consistent with other commands (most of them
don't take a direct argument). I think it’s also clearer in how the help text
works with it as a separate argument. Also, I don’t see a way to make the
argument required if it’s not a separate argument.
{quote}Can you please specify time in Min/Sec?{quote}
You have a good point here; I’ll make it in minutes.
Made the other changes you suggested as well.
> 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
>
>
> 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)
