[
https://issues.apache.org/jira/browse/OOZIE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118880#comment-14118880
]
Purshotam Shah commented on OOZIE-1567:
---------------------------------------
{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}
I didn't noticed that poll is as new command.
Doesn't it make more sense for poll to be part of job command, after all it's a
job operation.
oozie job -poll <job_id>
I also like your initial design of adding poll as part of -rerun/-submit.
Biggest use-case I see is that when user submit workflow/catchup mode coord or
rerun coord action/Wf, he would like to wait till completion.
In this case he have to run one more command to poll job status. I guess we can
do both.
> 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)
