[
https://issues.apache.org/jira/browse/OOZIE-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Subhashrao Saley updated OOZIE-2444:
-------------------------------------------
Attachment: OOZIE-2444-4-Doc.patch
> 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
> Fix For: trunk
>
> Attachments: OOZIE-2444-1.patch, OOZIE-2444-2.patch,
> OOZIE-2444-3.patch, OOZIE-2444-4-Doc.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)
