[ 
https://issues.apache.org/jira/browse/STORM-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997832#comment-13997832
 ] 

ASF GitHub Bot commented on STORM-320:
--------------------------------------

GitHub user chu11 opened a pull request:

    https://github.com/apache/incubator-storm/pull/114

    STORM-320: Support STORM_CONF_DIR environment variable to support

    Support STORM_CONF_DIR environment variable to support alternate location 
of storm.yaml file.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chu11/incubator-storm STORM-320

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-storm/pull/114.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 #114
    
----
commit c7b223824df12858f3029010d655b72f13d777fb
Author: Albert Chu <[email protected]>
Date:   2014-05-14T17:37:09Z

    STORM-320: Support STORM_CONF_DIR environment variable to support
    alternate location of storm.yaml file.

----


> Support STORM_CONF_DIR environment variable for alternate conf dir
> ------------------------------------------------------------------
>
>                 Key: STORM-320
>                 URL: https://issues.apache.org/jira/browse/STORM-320
>             Project: Apache Storm (Incubating)
>          Issue Type: Improvement
>    Affects Versions: 0.9.1-incubating
>            Reporter: Albert Chu
>            Priority: Minor
>         Attachments: STORM-320.patch
>
>
> In many apache big data projects (Hadoop, Hbase, to name a few), the user can 
> specify an alternate config file directory with PROJECT_CONF_DIR, such as 
> HADOOP_CONF_DIR or HBASE_CONF_DIR.
> It'd be useful to have this feature in Storm instead of hard coding a 
> different location into bin/storm.
> I've written a simple patch, which I will attach and also send a pull request 
> on github.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to