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-1942) Allow Falcon server and client classpath to be customizable
Date Tue, 10 May 2016 21:52:12 GMT

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

ASF GitHub Bot commented on FALCON-1942:
----------------------------------------

Github user asfgit closed the pull request at:

    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)

Mime
View raw message