You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Karthik K (Updated) (JIRA)" <ji...@apache.org> on 2012/01/31 03:44:10 UTC
[jira] [Updated] (FLUME-941) Load flume-env.sh from flume_conf_dir
environment variable / system property as opposed to bin directory
[ https://issues.apache.org/jira/browse/FLUME-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthik K updated FLUME-941:
----------------------------
Attachment: FLUME-941.patch
> Load flume-env.sh from flume_conf_dir environment variable / system property as opposed to bin directory
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLUME-941
> URL: https://issues.apache.org/jira/browse/FLUME-941
> Project: Flume
> Issue Type: Improvement
> Components: Shell
> Affects Versions: v1.0.0
> Reporter: Karthik K
> Assignee: Karthik K
> Fix For: v1.1.0
>
> Attachments: FLUME-941.patch
>
>
> When frequently trying out different installations / upgrades of flume, more than not, the flume installation directory (including ./bin) is nuked and replaced with an updated version for testing, but the flume settings are usually stored under FLUME_CONF_DIR , independently to preserve the settings.
> In the current code, the flume-env.sh(.template) is present in BINDIR to override.
> We want to provide a mechanism, to source from FLUME_CONFIG_DIR/flume-env.sh though, (if present) while being backward compatible still.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira