[
https://issues.apache.org/jira/browse/OOZIE-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114232#comment-15114232
]
Hadoop QA commented on OOZIE-2444:
----------------------------------
Testing JIRA OOZIE-2444
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does adds/modifies 3 testcase(s)
{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: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 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: 1710
. Tests failed: 5
. Tests errors: 2
. The patch failed the following testcases:
. testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
. testPurgeXCommandFailed(org.apache.oozie.command.TestPurgeXCommand)
. testPurgeWFWithSubWF1(org.apache.oozie.command.TestPurgeXCommand)
. testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)
.
testActionCheckTransientDuringLauncher(org.apache.oozie.command.wf.TestActionCheckXCommand)
{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/2721/
> Need conditional logic in bundles
> ---------------------------------
>
> Key: OOZIE-2444
> URL: https://issues.apache.org/jira/browse/OOZIE-2444
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Satish Subhashrao Saley
> Priority: Minor
> Attachments: OOZIE-2444-1.patch, OOZIE-2444-2.patch
>
>
> Sometimes, the users have a semi-complicated pipeline that needs to run in
> slightly different ways depending on whether they are running against live
> data, reprocessing recent data, or reprocessing historical data from another
> cluster. Instead of having to create multiple different bundles to capture
> these various cases, it would be good to have some sort of conditional logic
> in the bundle XML file that users can use to enable or disable specific
> coordinators within the bundle based on the properties passed in. That way,
> we can control, either from the properties file or from oozie command line
> options, the coordinators that get run and the mode that overall pipeline is
> processing in.
> Ideally, this would be supported by extending the <coordinator> tag with a
> new "enabled" attribute that takes a boolean expression and supports standard
> expression syntax and functions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
