[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585671#comment-14585671
]
Srikanth Sundarrajan commented on OOZIE-2030:
---------------------------------------------
There is perhaps a simpler way to tackle this issue. If we modify the
LiteWorkflowAppParser to serialize persist the contents of global in conf and
have handleGlobal() also consult conf for the handling section, this will
ensure that global is propagated correctly with no further changes to any other
section of the code, honoring the right overlay priorities. While the code in
LWAP wouldn't be specific to Subworkflows either. Luckily the conf itself is
propagates into subflows on user's request. - [~shwethags], [~rohini], makes
sense ?
> 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)
