[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620393#comment-14620393
]
Jaydeep Vishwakarma commented on OOZIE-2030:
--------------------------------------------
[~shwethags],
1. 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.
I will update the patch.
2. Also please base64 encode the setting value, in case it causes some issues
with the xml format.
I am keeping it in the text format to improve the debugging.
Let me know if you have any other concern?
> 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)
