[jira] [Updated] (OOZIE-1226) Workflow lib path not found in classpath for a subworkflow

["Robert Kanter (JIRA)" <ji...@apache.org>]

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

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

    Labels: incompatible  (was: )

Marking incompatible because in Oozie 3.3.2, it defaults to true (i.e. inheriting the jars) but in Oozie 4, it defaults to false (i.e. not inheriting the 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
>              Labels: incompatible
>             Fix For: 3.3.2
>
>         Attachments: OOZIE-1226.patch, OOZIE-1226_branch-3.3.patch, OOZIE-1226_branch-3.3.patch, OOZIE-1226_branch-3.3.patch, OOZIE-1226_trunk.patch, OOZIE-1226_trunk.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 was sent by Atlassian JIRA
(v6.2#6252)