[
https://issues.apache.org/jira/browse/OOZIE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054463#comment-16054463
]
Hadoop QA commented on OOZIE-2957:
----------------------------------
Testing JIRA OOZIE-2957
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
. {color:red}WARNING{color}: the current HEAD has 6 Javadoc warning(s)
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
. Tests run: 1770
. Tests rerun: 3
. Tests failed at first run:
org.apache.oozie.action.hadoop.TestHdfsOperations,
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3910/
> 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)
