[
https://issues.apache.org/jira/browse/OOZIE-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946107#comment-13946107
]
Hadoop QA commented on OOZIE-1746:
----------------------------------
Testing JIRA OOZIE-1746
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:red}-1{color} the patch contains 14 line(s) with tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:red}-1{color} the patch contains 9 line(s) longer than 132
characters
. {color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:red}-1 RAT{color}
. {color:red}-1{color} the patch seems to introduce 1 new RAT warning(s)
{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:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:red}-1{color} the patch seems to introduce 6 new javac warning(s)
{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: 1402
. Tests failed: 2
. Tests errors: 1
. The patch failed the following testcases:
.
testTimeOutWithUnresolvedMissingDependencies(org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand)
.
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)
{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/1122/
> New API to fetch workflows corresponding to coordinator action reruns
> ---------------------------------------------------------------------
>
> Key: OOZIE-1746
> URL: https://issues.apache.org/jira/browse/OOZIE-1746
> Project: Oozie
> Issue Type: New Feature
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: trunk
>
> Attachments: OOZIE-1746-0.patch, OOZIE-1746-1.patch,
> OOZIE-1746-2.patch, OOZIE-1746-3.patch
>
>
> The coordinator action's 'external id' only points to the latest workflow
> launched, in the case of rerun. We lose context of the previous workflows
> corresponding to this action and no easy API to retrieve them. This JIRA adds
> this API functionality for Web-service, web-console and CLI
> Usage:
> Web Service API:
> http://my-oozie-url:4080/oozie/v2/job/COORD-ID?getreruns=<action num>
> CLI: $> oozie job -info COORD-ID -getreruns <action-num>
> Web-console: New tab 'Coord Action Reruns' alongside Coord Job Info, Coord
> Definition etc.., to input the action num in text box and press button to get
> list of workflows
--
This message was sent by Atlassian JIRA
(v6.2#6252)
