You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/05/21 22:12:41 UTC

[jira] [Commented] (OOZIE-637) parametrization of 'name' attribute in workflow

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

Alejandro Abdelnur commented on OOZIE-637:
------------------------------------------

This should cover Workflow/Coordinator/Bundle applications. It should be OK to support it in ALL schemas as it does not break backwards compatibility.
                
> parametrization of 'name' attribute in workflow
> -----------------------------------------------
>
>                 Key: OOZIE-637
>                 URL: https://issues.apache.org/jira/browse/OOZIE-637
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Ryan McHale
>            Assignee: Alejandro Abdelnur
>
> Currently  user can't parametrize the name attribute of workflow or bundle.
> As a result, user needs to write a lot of xml with different names where content is same.
> Reason: Oozie does not support variable replacement for name and frequency.
> (<workflow-app xmlns="uri:oozie:workflow:0.2" name="${name}">
> 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. 

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