You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Parameswaran Raman (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/18 01:27:10 UTC

[jira] [Resolved] (OOZIE-567) Is sub-workflow lib directory not used?

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

Parameswaran Raman resolved OOZIE-567.
--------------------------------------

    Resolution: Fixed

Changes have been committed. Marking as fixed.
                
> Is sub-workflow lib directory not used?
> ---------------------------------------
>
>                 Key: OOZIE-567
>                 URL: https://issues.apache.org/jira/browse/OOZIE-567
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Parameswaran Raman
>
> Consider the subworkflow scenario as below:
> * Parent workflow is a subworkflow "subwf" with a required library oozie-examples.jar.
> * Child workflow is a java workflow "java-wf" with a required library main.jar
> On submitting the job, it is found that the libraries (.jars in this case) from the child workflow do not appear in the java class path or the mapred.cache. As a result, the job fails with "java.lang.RuntimeException: java.lang.ClassNotFoundException".
> The CLASSPATH of the job (taken from job log on JT) shows libraries that are in the main workflow, not the sub-workflow. However, when the .jars from child workflow were copied to the parent workflow, everything seems to work. This raises the question that whether the child workflows's lib directory is not used?
> Different Scenarios Tested:
> ------
> Parent Lib Directory contains oozie-examples.jar, Child Lib Directory contains main.jar => Application Fails
> Parent Lib Directory contains main.jar, Child Lib Directory is empty => Application Succeeds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira