You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2013/12/17 01:02:08 UTC

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

     [ https://issues.apache.org/jira/browse/OOZIE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohini Palaniswamy updated OOZIE-1504:
--------------------------------------

    Summary: Allow specifying a fixed instance as the start instance of a data-in  (was: parameterize coord EL functions (latest and current))

> 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)