You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/07/28 07:23:20 UTC
[jira] [Commented] (OOZIE-807) Docs can be explicit about multiple
sub-workflow definitions being possible
[ https://issues.apache.org/jira/browse/OOZIE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397168#comment-15397168 ]
Hadoop QA commented on OOZIE-807:
---------------------------------
Testing JIRA OOZIE-807
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}-1 COMPILE{color}
. {color:red}-1{color} HEAD does not compile
. {color:red}-1{color} patch does not compile
. {color:green}+1{color} the patch does not seem to introduce new javac warnings
{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:red}-1 TESTS{color}
. Tests run: 1791
. Tests failed: 1
. Tests errors: 0
. The patch failed the following testcases:
. testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
{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}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3132/
> Docs can be explicit about multiple sub-workflow definitions being possible
> ---------------------------------------------------------------------------
>
> Key: OOZIE-807
> URL: https://issues.apache.org/jira/browse/OOZIE-807
> Project: Oozie
> Issue Type: Improvement
> Components: docs
> Affects Versions: 3.2.0
> Reporter: Harsh J
> Assignee: Harsh J
> Priority: Trivial
> Attachments: OOZIE-807.patch, OOZIE-807.patch, OOZIE-807.patch
>
>
> With the feature that sub-workflows offer, a FAQ may be "Does Oozie allow multiple sub-workflow definitions in the same workflow?". I think the doc page about Sub-workflows should carry a line that makes it clear this is possible just in the same way as other action types.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)