[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583171#comment-14583171
]
Jaydeep Vishwakarma commented on OOZIE-2030:
--------------------------------------------
[~sriksun], I have added the same patch in review board.
Comments on your review.
context.workflow does not have global section. Handle global already extracting
all the global section conf from there. Global conf is merge with other conf. I
will not be able to figure out which conf values belongs to global.
{{jobConf.get(SubWorkflowActionExecutor.SUBWF_JOBCONF)}} will be able to go N
number of levels without any issue.
{fetchGlobalConf(ns, parentGlobalElement, global);}} and
{{elem.addContent((Element)global.clone());}} ensuring it.
I am asserting three values in test case, where {{foo2}} belongs to both both
workflow global conf. If you check the test case {{foo2}} have subworkflow's
value instead of workflow.
> 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)
