[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626013#comment-14626013
]
Srikanth Sundarrajan commented on OOZIE-2030:
---------------------------------------------
>From what I understood there were 2 concerns with the patch
1> Not removing the global conf from workflow conf before persistence
2> Not encoding global conf and using xml as is
Given the global section is being added only to the workflow conf (in
compressed state), am assuming there isn't much storage overhead and retaining
the conf in xml format, might not be all that bad as long as there is no direct
string manipulation of xmls.
Any further work needed on the patch ?
> 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-v5.patch, OOZIE-2030-v6.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)
