[ 
https://issues.apache.org/jira/browse/CASSANDRA-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887264#action_12887264
 ] 

dopsun commented on CASSANDRA-1126:
-----------------------------------

Well, actually the subject of this issue is: loading cassandra.yaml from 
location other class path. So, the first patch is the right one :-). The one I 
uploaded actually cannot be the implementation for the requirements. Since it 
still load the file from class path.

I'm uploading patch as you suggested for this JIRA because I found it's 
scheduled for 0.7.0 andI believe that there are needs to using different file 
name other than (cassandra.yaml) and/ or different location. It will give big 
flexibility for automate starting process (as stated by Erik). From this point 
of view, both first one and second one can work.

For using variable in .sh script, is the value of the CASSANDRA_CONF is a 
absolute path? if it is, i believe it's similar with first approach, if it's 
file name only, it's similar to the second approach. Agree?



> Allow loading of cassandra.yaml from a location off the classpath
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-1126
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1126
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7
>            Reporter: Erik Onnen
>            Priority: Trivial
>             Fix For: 0.7
>
>         Attachments: DatabaseDescriptor.java.2.patch, 
> DatabaseDescriptor.java.patch
>
>
> As a convenience, predominantly for testing but also for some levels of 
> automated ops, it would be helpful to allow cassandra.yaml to be specified 
> explicitly during startup as opposed to always reading it from the classpath 
> which cannot be altered at runtime (not easily anyway).
> Sample patch attached that reads -D property cassandra.conf and gives it 
> preference over any entry on the classpath.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to