[
https://issues.apache.org/jira/browse/OOZIE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121600#comment-13121600
]
[email protected] commented on OOZIE-567:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2156/#review2377
-----------------------------------------------------------
Ship it!
+1
- Angelo K.
On 2011-10-04 03:40:26, params wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2156/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-10-04 03:40:26)
bq.
bq.
bq. Review request for oozie, Mohammad Islam and Angelo K. Huang.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. OOZIE-567: Is sub-workflow lib directory not used?
bq.
bq. Summary:
bq. https://issues.apache.org/jira/browse/OOZIE-567
bq.
bq.
bq. This addresses bug OOZIE-567.
bq. https://issues.apache.org/jira/browse/OOZIE-567
bq.
bq.
bq. Diffs
bq. -----
bq.
bq.
trunk/core/src/main/java/org/apache/oozie/service/WorkflowAppService.java
1178596
bq.
trunk/core/src/test/java/org/apache/oozie/service/TestLiteWorkflowAppService.java
1178596
bq. trunk/release-log.txt 1178596
bq.
bq. Diff: https://reviews.apache.org/r/2156/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Tested against current test cases. Added two new test cases.
bq.
bq.
bq. Thanks,
bq.
bq. params
bq.
bq.
> 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
