[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239002#comment-14239002
]
Shwetha G S commented on OOZIE-2030:
------------------------------------
[~rohini],
oozie.launcher.* is added as well.
Currently, the properties from conf/job-xml are available as a file which can
be loaded in java launcher. But they are not available as default conf. Having
them as default conf is useful and simpler if java action is used as a
driver(which is the case most of the times). This patch adds the properties
from conf/job-xm in the launcher job conf and oozie.launcher.* overrides.
This is not backward compatible. If this doesn't work for some, I can add this
based on config. Let me know
> 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: Shwetha G S
> Attachments: OOZIE-2030-v2.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)
