[
https://issues.apache.org/jira/browse/OOZIE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated OOZIE-515:
-------------------------------------
Fix Version/s: pre-Apache
> OOZIE-98: parametrization of 'name' attribute in workflow/coordinator/bundle
> ----------------------------------------------------------------------------
>
> Key: OOZIE-515
> URL: https://issues.apache.org/jira/browse/OOZIE-515
> Project: Oozie
> Issue Type: New Feature
> Reporter: Mohammad Kamrul Islam
> Assignee: Mohammad Kamrul Islam
> Fix For: pre-Apache
>
>
> Currently user can't parametrize the name attribute of workflow/coordinator
> or bundle.
> As a result, user needs to write a lot of xml with different names where
> content is same.
> Moreover, if it is allowed, user could do a query with a pattern.
> Oozie user at Y1 has described the issue as follows:
> Our framework generates the properties and the coordinator xml's for various
> frequencies and various regions.
> Currently, we generate a single coordinator.xml and multiple .properties
> files (corresponding to diff timezone) for a
> particular frequency.
> Problem: our SE are not able to identify the app names by their timezones as
> there is only one coordinator.xml with a
> hardcoded app name.
> Reason: Oozie does not support variable replacement for name and frequency.
> (<coordinator-app name="${name}" frequency="{$freq}"...>
> But it supports substitutions for other parameters such as timezone, start
> and end.
> It gives an XML schema error, cvc-pattern-valid: Value '${name}' is not a
> facet-valid with respect to pattern....
> If this replacement is allowed we could get this name from the .properties
> file instead of hardcoding the app name in
> the xml.
> The other solution is to have multiple coordinator.xml's corresponding to the
> number of .properties files (timezones).
> But this results in redundancy just for one app name difference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
