[
https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107344#comment-15107344
]
Robert Kanter commented on OOZIE-2030:
--------------------------------------
In our testing, we ran into a situation where you could get an NPE from this
change. I've filed OOZIE-2441 to fix it.
> 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
> Fix For: trunk
>
> Attachments: OOZIE-2030-v10.patch, OOZIE-2030-v11.patch,
> OOZIE-2030-v12.patch, OOZIE-2030-v2.patch, OOZIE-2030-v3.patch,
> OOZIE-2030-v4.patch, OOZIE-2030-v5.patch, OOZIE-2030-v6.patch,
> OOZIE-2030-v7.patch, OOZIE-2030-v8.patch, OOZIE-2030-v8.patch,
> OOZIE-2030-v9.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)