[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585630#comment-14585630
]
Shwetha G S commented on OOZIE-2030:
------------------------------------
[~rohini],
SubWorkflowActionExecutor launches new workflow with app path = suborkflow app
path. Sub workflow will read the global conf from this subworkflow app path.
Merging the global sections requires modifying the workflow.xml from this
subworkflow app path which we don't want to touch, right? So, only other way is
to set the global conf as a conf while launching subworkflow and workflow
parser of sub workflow will do the merge. Makes sense? So, this requires
changes in LiteWorkflowAppParser
> Configuration properties from global section is not getting set in Hadoop job
> conf when using sub-workflow action in Oozie workflow.xml
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-2030
> URL: https://issues.apache.org/jira/browse/OOZIE-2030
> Project: Oozie
> Issue Type: Bug
> Components: action
> Reporter: Peeyush Bishnoi
> Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2030-v2.patch, OOZIE-2030-v3.patch,
> OOZIE-2030-v4.patch, OOZIE-2030.patch
>
>
> When submitting Oozie workflow with sub-workflow action and with global
> section, configuration properties defined in global section is not getting
> set in launched Hadoop job conf. But when we use Pig or MR action in
> workflow.xml, configuration properties from global section set properly into
> Hadoop job conf.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
