[
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_trunk.patch
OOZIE-1226_branch-3.3.patch
I added a switch in oozie-site and a switch in job.properties. If present, the
switch in job.properties has priority. I also added documentation.
I think we should keep the current expected behavior (i.e. inheriting parent
jars) as the default in the 3.x line, but switch to not inheriting the parent
jars by default in the 4.x line, so I've created two patches. The only
difference between them is that it defaults to true in
OOZIE-1226_branch-3.3.patch and defaults to failse in OOZIE-1226_trunk.patch
(and documentation accordingly).
> 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
>
>
> 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
