[
https://issues.apache.org/jira/browse/OOZIE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated OOZIE-2957:
---------------------------------
Attachment: OOZIE-2957-1.patch
> Documentation states that starting a coordinator is possible
> ------------------------------------------------------------
>
> Key: OOZIE-2957
> URL: https://issues.apache.org/jira/browse/OOZIE-2957
> Project: Oozie
> Issue Type: Bug
> Components: coordinator, docs
> Affects Versions: 5.0.0
> Reporter: Jan Hentschel
> Assignee: Jan Hentschel
> Attachments: OOZIE-2957-1.patch
>
>
> The documentation of the command line tools states that starting a
> coordinator is possible
> {quote}---+++ Starting a Workflow, Coordinator or Bundle Job
> Example:
> <verbatim>
> $ oozie job -oozie http://localhost:11000/oozie -start
> 14-20090525161321-oozie-joe
> </verbatim>
> The =start= option starts a previously submitted workflow job, coordinator
> job or bundle job that is in =PREP= status.
> After the command is executed the workflow job will be in =RUNNING= status,
> coordinator job will be in =RUNNING= status and
> bundle job will be in =RUNNING=status.{quote}
> As of OOZIE-923 this should not be possible. The documentation should be
> changed to not include coordinators in this section or mention that starting
> a coordinator from the CLI is not possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
