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

Posted to dev@falcon.apache.org by "Venkat Ranganathan (JIRA)" <ji...@apache.org> on 2016/05/10 20:57:12 UTC

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

Venkat Ranganathan created FALCON-1942:
------------------------------------------

             Summary: 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: 0.10


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)