[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586535#comment-14586535
]
Rohini Palaniswamy commented on OOZIE-2030:
-------------------------------------------
Agree. If we are serializing whole global section into conf, need to ensure
that the serialized conf does not end up in multiple places - each action conf,
job.xml on hdfs, etc which will bloat size a lot and that inefficiency will end
up being a problem at scale. So [~jaydeepvishwakarma], in the implementation
take care to only process that serialized config in LiteWorkflowAppParser and
throw it away before the actionconf is constructed and stored in database.
[~rkanter] has done some cleanup of the global section in OOZIE-2187. Would be
good to base your patch on top of that.
Also please base64 encode the setting value, in case it causes some issues with
the xml format.
> 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)
