You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Jeremy Beard (JIRA)" <ji...@apache.org> on 2014/05/19 20:36:39 UTC
[jira] [Updated] (OOZIE-1851) Global NN and JT values are not
propagated to subworkflows
[ https://issues.apache.org/jira/browse/OOZIE-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Beard updated OOZIE-1851:
--------------------------------
Description:
<name-node> and <job-tracker> values under <global> are not passed to a subworkflow's <global> section when using <propagate-configuration/>.
Implementing this would be very useful for reducing clutter in subworkflow definitions.
was:<name-node> and <job-tracker> values under <global> are not passed to a subworkflow's <global> section when using <propagate-configuration/>. Implementing this would be very useful for reducing clutter in subworkflow definitions.
> Global NN and JT values are not propagated to subworkflows
> ----------------------------------------------------------
>
> Key: OOZIE-1851
> URL: https://issues.apache.org/jira/browse/OOZIE-1851
> Project: Oozie
> Issue Type: Bug
> Components: workflow
> Affects Versions: 4.0.0
> Reporter: Jeremy Beard
>
> <name-node> and <job-tracker> values under <global> are not passed to a subworkflow's <global> section when using <propagate-configuration/>.
> Implementing this would be very useful for reducing clutter in subworkflow definitions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)