You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:25:09 UTC

[jira] [Commented] (OOZIE-73) GH-27: add support for a share lib directory in HDFS for action binaries.

    [ https://issues.apache.org/jira/browse/OOZIE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099769#comment-13099769 ] 

Hadoop QA commented on OOZIE-73:
--------------------------------

tucu00 remarked:
Closed by 403aeea1dc2218d566eba670dbc905a90139c958 add support for a share lib directory in HDFS for action binaries.

If the 'oozie.libpath' (OozieClient.LIBPATH) property is set in the job properties
when submitting a job. The contents JAR files and SO files in the specified directory
will be added to the job classpath/libpath following the workflow's lib/ directory
files (the workflow's lib/ directory files have precedence).

This patch leverage the functionalitly added for MR/PIG http submisison.

> GH-27: add support for a share lib directory in HDFS for action binaries.
> -------------------------------------------------------------------------
>
>                 Key: OOZIE-73
>                 URL: https://issues.apache.org/jira/browse/OOZIE-73
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> Currently every workflow that uses a pig action must bundle the Pig JAR in the workflow lib/ directory.
> This is also true for commonly use JARs files across different workflow apps.
> By adding a share lib job property, which is added as a secondary lib/ directory, all commons JARs (Pig, Hive) can be added in a /usr/share/lib directory in HDFS and used by multiple workflow applications without having to have a private copy per workflow app.
> The location of HDFS share lib would be specified as job property (a later rev of the workflow XML schema may add support for it too)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira