You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@falcon.apache.org by "Balu Vellanki (JIRA)" <ji...@apache.org> on 2016/05/10 21:52:12 UTC

[jira] [Resolved] (FALCON-1942) Allow Falcon server and client classpath to be customizable

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

Balu Vellanki resolved FALCON-1942.
-----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 0.10)
                   trunk

Issue resolved by pull request 134
[https://github.com/apache/falcon/pull/134]

> Allow Falcon server and client classpath to be customizable
> -----------------------------------------------------------
>
>                 Key: FALCON-1942
>                 URL: https://issues.apache.org/jira/browse/FALCON-1942
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Venkat Ranganathan
>            Assignee: Venkat Ranganathan
>             Fix For: trunk
>
>
> Currently, in falcon-config, we initialize the falcon classpath (for both client and servers).   The FALCONCPPATH variable is fully initialized and constructed within the config script. 
> With the addition of features like Atlas integration and also with extension feature, there are scenarios where we would have to allow additional classpath elements to be added to server/client invocations. 
> We should have a mechanism to do that



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)