[jira] [Commented] (OOZIE-1504) Allow specifying a fixed instance as the start instance of a data-in

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850094#comment-13850094 ] 

Hadoop QA commented on OOZIE-1504:
----------------------------------

Testing JIRA OOZIE-1504

Cleaning local svn 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 2 line(s) with tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:red}-1{color} the patch contains 1 line(s) longer than 132 characters
.    {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:green}+1 TESTS{color}
.    Tests run: 1376
{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/952/

> Allow specifying a fixed instance as the start instance of a data-in
> --------------------------------------------------------------------
>
>                 Key: OOZIE-1504
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1504
>             Project: Oozie
>          Issue Type: Improvement
>    Affects Versions: trunk
>            Reporter: Ryota Egashira
>            Assignee: purshotam shah
>             Fix For: trunk
>
>         Attachments: OOZIE-1504_v4.patch
>
>
> for example, coordinator.xml
> -----
>     <input-events>
>          <data-in name="foo" dataset="bar">
>             <start-instance>${coord:latest(-365)}</start-instance>
>             <end-instance>${coord:latest(0)}</end-instance>
>          </data-in>
>     </input-events>
> -----
> there are use cases to use the same coordinator.xml for varying number of data instances (not always 365). but the parameter to coord EL function cannot be parametrized (by using job
> config), customer needs to copy coordinator.xml with different number just to change the parameter of coord:latest(), which is not optimal for maintenance.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)