[
https://issues.apache.org/jira/browse/OOZIE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578930#comment-13578930
]
Alejandro Abdelnur commented on OOZIE-1226:
-------------------------------------------
It looks good, 2 things though:
The var that has the Oozie server value should be named
'oozieSubWfCPInheritance'
The code:
{code}
boolean subwfCPInheritance = subworkflowCPInheritance;
String WFsubworkflowCPInheritance =
jobConf.get(OOZIE_WF_SUBWORKFLOW_CLASSPATH_INHERITANCE);
if (WFsubworkflowCPInheritance != null) {
subwfCPInheritance =
(WFsubworkflowCPInheritance.equals("true"));
}
{code}
could be simplified as:
{code}
boolean oozieSubWfCPInheritance =
jobConf.getBoolean(OOZIE_WF_SUBWORKFLOW_CLASSPATH_INHERITANCE,
oozieSubWfCPInheritance);
{code}
> Workflow lib path not found in classpath for a subworkflow
> ----------------------------------------------------------
>
> Key: OOZIE-1226
> URL: https://issues.apache.org/jira/browse/OOZIE-1226
> Project: Oozie
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Assignee: Robert Kanter
> Fix For: trunk, 3.3.2
>
> Attachments: OOZIE-1226_branch-3.3.patch, OOZIE-1226.patch,
> OOZIE-1226_trunk.patch, OOZIE-1226_trunk.patch
>
>
> Currently only the jars in lib path of the subworkflow are added to classpath
> and the jars in lib path of the parent workflow are not.
> History:
> OOZIE-567 added support for adding subworkflow libpath to the classpath in
> addition to parent workflow libpath. OOZIE-871 had a change to avoid
> duplicate values, but caused the subworkflow libpath to be overwritten by
> parent workflow's libpath. OOZIE-981 caused the subworkflow libpath to be
> taken into account, but the parent workflow libpath was overwritten.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
