[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621974#comment-14621974
]
Jaydeep Vishwakarma commented on OOZIE-2030:
--------------------------------------------
[~rohini], [~shwethags],
What is the patch doing
1. It is adding oozie.globalconf in workflow if global conf is present
2. It is adding oozie.globalconf in subworkflow if any of the ancestor workflow
have global conf.
What is being additionally added into Oozie State
1. It will keep global conf in text format.
2. Workflow and subworkflow will have additional payload for global conf in DB.
Why I am inclined to retain the patch as it is
1. Keep the conf in text format instead of Base64 will improve the
debuggability of code.
2. Removing global conf from workflow after using it will make it hacky. It
will make difficult for developer to understand that there was some property
which passed to the workflow action.
> 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)
