[jira] [Resolved] (OOZIE-552) OOZIE-135: support multiple shared lib path in oozie

["Angelo K. Huang (JIRA)" <ji...@apache.org>]

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

Angelo K. Huang resolved OOZIE-552.
-----------------------------------

    Resolution: Fixed
      Assignee: chao wang  (was: Roman Shaposhnik)

fixed in 3.1

> OOZIE-135: support multiple shared lib path in oozie
> ----------------------------------------------------
>
>                 Key: OOZIE-552
>                 URL: https://issues.apache.org/jira/browse/OOZIE-552
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Hadoop QA
>            Assignee: chao wang
>
> It would be great if oozie.libpath can take more than one path. That would help to modularize the shared library directory. A user specifies all shared library paths used by the workflow and Oozie combines the resources into one. 
> For example, my wf contains 2 actions - one pig action + one hive action.
> I can have:
> libpath=/user/share/pig-0.7,/user/share/hive-0.6.
> Otherwise, I have to put everything into one single huge /user/share/common/, which can become cumbersome.
> Note: the shared library path (either a single path or multiple paths) is to allow somebody to sanitize all share dependencies and then easily use them without conflicts, so it needs to be checked carefully before use to ensure there is no class or any other conflicts.

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