[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238727#comment-14238727
]
Rohini Palaniswamy commented on OOZIE-2030:
-------------------------------------------
bq. I am adding properties from configuration and job-xml as launcher job
properties for java actions
The standard has been to prefix launcher properties with oozie.launcher. Are
we going against that?
> 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)
