You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Ryan McHale (Created) (JIRA)" <ji...@apache.org> on 2011/12/15 04:19:30 UTC
[jira] [Created] (OOZIE-637) parametrization of 'name' attribute in
workflow
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: Mohammad Kamrul Islam
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
[jira] [Commented] (OOZIE-637) parametrization of 'name' attribute
in workflow/coordinator/bundle
Posted by "Mona Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280560#comment-13280560 ]
Mona Chitnis commented on OOZIE-637:
------------------------------------
In BundleSubmitXCommand, the call to bundleJob.setAppName() is being done twice.
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, workflow
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch
>
>
> 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
[jira] [Assigned] (OOZIE-637) parametrization of 'name' attribute
in workflow
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur reassigned OOZIE-637:
----------------------------------------
Assignee: Alejandro Abdelnur (was: Mohammad Kamrul Islam)
Mohammad, stealing this issue from you as I need this feature and it has been inactive for 6 months. Please let me know if you are not OK with this.
> 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
[jira] [Updated] (OOZIE-637) parametrization of 'name' attribute in
workflow
Posted by "Ryan McHale (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McHale updated OOZIE-637:
------------------------------
Description:
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.
was:
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.
> 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: Mohammad Kamrul Islam
>
> 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
[jira] [Updated] (OOZIE-637) parametrization of 'name' attribute in
workflow/coordinator/bundle
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated OOZIE-637:
-------------------------------------
Component/s: workflow
coordinator
bundle
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, workflow
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch
>
>
> 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
[jira] [Commented] (OOZIE-637) parametrization of 'name' attribute
in workflow
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (OOZIE-637) parametrization of 'name' attribute
in workflow/coordinator/bundle
Posted by "Mona Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280628#comment-13280628 ]
Mona Chitnis commented on OOZIE-637:
------------------------------------
Yes I suppose so. The bundle-submit-job.xml can have parametrized name for coord so we can test this case as well. In XDataTestCase.createBundleJob, you can remove the explicit setting of bundle appName.
Looks good. +1
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, workflow
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch, OOZIE-637.patch
>
>
> 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
[jira] [Updated] (OOZIE-637) parametrization of 'name' attribute in
workflow/coordinator/bundle
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated OOZIE-637:
-------------------------------------
Attachment: OOZIE-637.patch
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch
>
>
> 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
[jira] [Commented] (OOZIE-637) parametrization of 'name' attribute
in workflow/coordinator/bundle
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280655#comment-13280655 ]
Virag Kothari commented on OOZIE-637:
-------------------------------------
+1
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, workflow
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch, OOZIE-637.patch
>
>
> 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
[jira] [Commented] (OOZIE-637) parametrization of 'name' attribute
in workflow/coordinator/bundle
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280629#comment-13280629 ]
Alejandro Abdelnur commented on OOZIE-637:
------------------------------------------
@Mona, have to have the createBundleJob setting to test that vars work in bundle name. thx
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, workflow
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch, OOZIE-637.patch
>
>
> 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
[jira] [Commented] (OOZIE-637) parametrization of 'name' attribute
in workflow/coordinator/bundle
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280605#comment-13280605 ]
Alejandro Abdelnur commented on OOZIE-637:
------------------------------------------
Mmmmh, I assume that in the case of bundles name injection, props will be resolved in the bundle before getting to the coordinator, no?
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, workflow
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch, OOZIE-637.patch
>
>
> 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
[jira] [Updated] (OOZIE-637) parametrization of 'name' attribute in
workflow/coordinator/bundle
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated OOZIE-637:
-------------------------------------
Summary: parametrization of 'name' attribute in workflow/coordinator/bundle (was: parametrization of 'name' attribute in workflow)
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> 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
[jira] [Updated] (OOZIE-637) parametrization of 'name' attribute in
workflow/coordinator/bundle
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated OOZIE-637:
-------------------------------------
Attachment: OOZIE-637.patch
Mona, thanks for catching that. I've missed (this assign to itself was done originally as well). Updated patch
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, workflow
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch, OOZIE-637.patch
>
>
> 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
[jira] [Commented] (OOZIE-637) parametrization of 'name' attribute
in workflow/coordinator/bundle
Posted by "Mona Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280597#comment-13280597 ]
Mona Chitnis commented on OOZIE-637:
------------------------------------
Also, in CoordinatorSubmitX, for the else case where coord job is created by bundle, it gets the app name from the BundleStartX. Resolution will be required to be done there too.
> parametrization of 'name' attribute in workflow/coordinator/bundle
> ------------------------------------------------------------------
>
> Key: OOZIE-637
> URL: https://issues.apache.org/jira/browse/OOZIE-637
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, workflow
> Affects Versions: 3.2.0, trunk
> Reporter: Ryan McHale
> Assignee: Alejandro Abdelnur
> Fix For: trunk
>
> Attachments: OOZIE-637.patch, OOZIE-637.patch
>
>
> 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