falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-887) Support for multiple lib paths in falcon process
Date Wed, 10 Feb 2016 23:10:18 GMT

    [ https://issues.apache.org/jira/browse/FALCON-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141915#comment-15141915

ASF GitHub Bot commented on FALCON-887:

GitHub user sowmyaramesh opened a pull request:


    FALCON-887 Support for multiple lib paths in falcon process


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sowmyaramesh/falcon FALCON-887

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #38
commit ad4d455b1363bb7ba39998dd430a49985d4b69dd
Author: Sowmya Ramesh <sramesh@hortonworks.com>
Date:   2016-02-10T23:08:35Z

    FALCON-887 Support for multiple lib paths in falcon process


> Support for multiple lib paths in falcon process
> ------------------------------------------------
>                 Key: FALCON-887
>                 URL: https://issues.apache.org/jira/browse/FALCON-887
>             Project: Falcon
>          Issue Type: New Feature
>          Components: process
>            Reporter: Akshay Goyal
>            Assignee: Sowmya Ramesh
>            Priority: Minor
> Cases where I have multiple jobs which use common libraries and also have some libraries
specific to each job. There are two options:
> 1: To use same lib path for all jobs which has all libraries (common and specific). But
all the jobs will end up loading all libraries.
> 2: To use a central lib location for common libraries and another lib location which
is specific to the job. 
> We can enable this by supporting comma separated lib paths in falcon process.

This message was sent by Atlassian JIRA

View raw message