[jira] [Resolved] (FLUME-941) Load flume-env.sh from flume_conf_dir environment variable / system property as opposed to bin directory

["Ashish Paliwal (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashish Paliwal resolved FLUME-941.
----------------------------------
    Resolution: Won't Fix

Won't fix. 0.X branch not maintained anymore

> 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: v0.9.4
>            Reporter: Karthik K
>            Assignee: Karthik K
>             Fix For: v0.9.5
>
>         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 was sent by Atlassian JIRA
(v6.3.4#6332)