[jira] [Commented] (OOZIE-2601) Ability to use local paths for the sharelib

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on OOZIE-2601:
----------------------------------

Testing JIRA OOZIE-2601

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:red}-1{color} the patch contains 1 line(s) with trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 132
.    {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
.    {color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.    Tests run: 1967
.    Tests rerun: 64
.    Tests failed at first run: org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.action.hadoop.TestLauncherAM,
{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}

{color:red}. There is at least one warning, please check{color}

The full output of the test-patch run is available at

. https://builds.apache.org/job/oozie-trunk-precommit-build/3961/

> Ability to use local paths for the sharelib
> -------------------------------------------
>
>                 Key: OOZIE-2601
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2601
>             Project: Oozie
>          Issue Type: New Feature
>    Affects Versions: oya
>            Reporter: Robert Kanter
>            Assignee: Attila Sasvari
>             Fix For: oya
>
>         Attachments: OOZIE-2601-01.patch
>
>
> With OOZIE-2590, as part of OOZIE-1770 Oozie on Yarn work, Oozie now has full control over the classpath given to the Launcher AM.  In a cluster where all nodes have everything installed locally (in the same paths), it should be possible to have the Launcher AM reference the local jars instead of having to localize them from HDFS.
> For example, if you have Hive installed on all nodes at {{/usr/lib/hive/}} and all Hive jars under {{/usr/lib/hive/lib/}}, we could have the Launcher AM add {{/usr/lib/hive/lib}} to its classpath.  This saves on the overhead of localizing the same jars from the hive sharelib in HDFS.  
> I think the best way to implement this is to augment the [Sharelib Mapping File|https://oozie.apache.org/docs/4.2.0/AG_Install.html#Oozie_Share_Lib] feature to accept {{file:///}} paths.
> If we had this also work with the "oozie" sharelib and the Oozie jars in the individual sharelibs (e.g. have the Mapping file take comma-separated dirs/jars), then in a cluster with everything installed on all of the nodes, you wouldn't need to bother with the sharelib at all!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)