[ https://issues.apache.org/jira/browse/OOZIE-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088771#comment-15088771 ]
Hadoop QA commented on OOZIE-1976: ---------------------------------- Testing JIRA OOZIE-1976 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 11 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:red}-1 BACKWARDS_COMPATIBILITY{color} . {color:red}-1{color} the patch seems to change 2 line(s) with 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: 1749 . Tests failed: 8 . Tests errors: 0 . The patch failed the following testcases: . testBundleRerunInPausedWithError(org.apache.oozie.command.bundle.TestBundleRerunXCommand) . testSamplers(org.apache.oozie.util.TestMetricsInstrumentation) . testBundleStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService) . testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC) . testbulkWfKillSuccess(org.apache.oozie.command.wf.TestBulkWorkflowXCommand) . testForNoDuplicates(org.apache.oozie.event.TestEventGeneration) . testPurgeWFWithSubWF1(org.apache.oozie.command.TestPurgeXCommand) . testPurgeXCommandFailed(org.apache.oozie.command.TestPurgeXCommand) {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/2703/ > Specifying coordinator input datasets in more logical ways > ---------------------------------------------------------- > > Key: OOZIE-1976 > URL: https://issues.apache.org/jira/browse/OOZIE-1976 > Project: Oozie > Issue Type: New Feature > Components: coordinator > Affects Versions: trunk > Reporter: Mona Chitnis > Assignee: Purshotam Shah > Fix For: trunk > > Attachments: Input-check.docx, OOZIE-1976-V3.patch, > OOZIE-1976-WIP.patch, OOZIE-1976-rough-design-2.pdf, > OOZIE-1976-rough-design.pdf > > > All dataset instances specified as input to coordinator, currently work on > AND logic i.e. ALL of them should be available for workflow to start. We > should enhance this to include more logical ways of specifying availability > criteria e.g. > * OR between instances > * minimum N out of K instances > * delta datasets (process data incrementally) > Use-cases for this: > * Different datasets are BCP, and workflow can run with either, whichever > arrives earlier. > * Data is not guaranteed, and while $coord:latest allows skipping to > available ones, workflow will never trigger unless mentioned number of > instances are found. > * Workflow is like a ‘refining’ algorithm which should run after minimum > required datasets are ready, and should only process the delta for efficiency. > This JIRA is to discuss the design and then the review the implementation for > some or all of the above features. -- This message was sent by Atlassian JIRA (v6.3.4#6332)