[ 
https://issues.apache.org/jira/browse/OOZIE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-1226:
---------------------------------

    Attachment: OOZIE-1226.patch

The patch now adds the jars from the parent workflow to the child workflow and 
makes sure there are no jars with the same name.  Also added some tests to 
verify different scenarios with this.  

I also ran a modified version of the subwf example and verified that the 
classpath had the correct jars.
                
> 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
>         Attachments: OOZIE-1226.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

Reply via email to