You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2013/11/01 05:08:17 UTC
[jira] [Commented] (FALCON-162) Update falcon scripts to let the
user set the log and pid locations.
[ https://issues.apache.org/jira/browse/FALCON-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811020#comment-13811020 ]
Srikanth Sundarrajan commented on FALCON-162:
---------------------------------------------
All the patch versions have the same name. I am assuming it is the latest. Please confirm.
> Update falcon scripts to let the user set the log and pid locations.
> --------------------------------------------------------------------
>
> Key: FALCON-162
> URL: https://issues.apache.org/jira/browse/FALCON-162
> Project: Falcon
> Issue Type: Bug
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: FALCON-162.patch, FALCON-162.patch, FALCON-162.patch
>
>
> Current falcon scripts hard code the location of the log and the pid dirs. Instead if we added the ability to source a falcon-env.sh which the user could provide then the user can overwrite these locations to some thing else.
> This would also allow the user a way to set JAVA_HOME and other env vars in a file rather than doing it in a shell. This is something similar to how hadoop works.
> Along with this change i also plan on changing the classpath to list dir/* instead of every jar file. Again this is similar to what hadoop 2 does.
--
This message was sent by Atlassian JIRA
(v6.1#6144)