You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Dénes Bodó (Jira)" <ji...@apache.org> on 2021/06/22 14:38:00 UTC

[jira] [Updated] (OOZIE-1851) Global NameNone (NN) and JobTracker/ResourceManager(JT/RM) values are not propagated to subworkflows

     [ https://issues.apache.org/jira/browse/OOZIE-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dénes Bodó updated OOZIE-1851:
------------------------------
    Summary: Global NameNone (NN) and JobTracker/ResourceManager(JT/RM) values are not propagated to subworkflows  (was: Global NN and JT values are not propagated to subworkflows)

> Global NameNone (NN) and JobTracker/ResourceManager(JT/RM) values are not propagated to subworkflows
> ----------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1851
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1851
>             Project: Oozie
>          Issue Type: Improvement
>          Components: workflow
>    Affects Versions: 4.0.0
>            Reporter: Jeremy Beard
>            Priority: Major
>
> <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
(v8.3.4#803005)