[ https://issues.apache.org/jira/browse/OOZIE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561523#comment-14561523 ]
Jaydeep Vishwakarma commented on OOZIE-2030: -------------------------------------------- I tried to follow same approach, But global element of sub-workflow and parent workflow is not coming in SubWorkflowActionExecutor.java. I have done some changes LiteWorkflowAppParser.java this will ensure for multi level pass of global element and will give the priority to sub-workflow properties. To verify the priority of sub-workflow properties i have modified the test case as well. > 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.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)