[
https://issues.apache.org/jira/browse/OOZIE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123709#comment-14123709
]
Purshotam Shah commented on OOZIE-1567:
---------------------------------------
{quote}
I think we should leave both at minutes (the last patch from yesterday).
{quote}
[~rkanter]] Can you please put final patch? We went back and forth multiple
times, so not sure which patch to review.
Regarding testing, you can use {{TestOozieCLI}} to test cli options.
Can you also create two different JIRA,
1.
{quote}
We use getCoordJobInfo API to get job status ,which fetches every column from
DB ( this can be fixed later, we can have a API just to report status).
{quote}
We should avoid fetching unneeded columns.
2.
{quote}
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.
{quote}
We should explore and see how can we do this? Running/rerunning and polling in
same command will be useful for users.
> 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, 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)
