[
https://issues.apache.org/jira/browse/FALCON-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278959#comment-15278959
]
ASF GitHub Bot commented on FALCON-1942:
----------------------------------------
GitHub user vrangan opened a pull request:
https://github.com/apache/falcon/pull/134
FALCON-1942: Allow Falcon server and client classpath to be customizable
Allow server and client classpath to be customizable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrangan/falcon FALCON-1942
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/falcon/pull/134.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #134
----
commit 1fe420fe88005fa6ea6d691f12553bc12e4d6b76
Author: Venkat Ranganathan <[email protected]>
Date: 2016-05-10T21:19:10Z
FALCON-1942: Allow Falcon server and client classpath to be customizable
----
> 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)
