[ https://issues.apache.org/jira/browse/CASSANDRA-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895730#action_12895730 ]
Nick Bailey commented on CASSANDRA-1126: ---------------------------------------- The patch in CASSANDRA-1347 modifies cassandra.in.sh to only modify CASSANDRA_CONF if it is not already set. Not exactly the goal of the title of this ticket but allows for the same result. Personally I don't really see a need for being able to rename the configuration files. > Allow loading of cassandra.yaml from a location given on the commandline > ------------------------------------------------------------------------ > > Key: CASSANDRA-1126 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1126 > Project: Cassandra > Issue Type: Improvement > Components: Core > Affects Versions: 0.7 beta 1 > Reporter: Erik Onnen > Priority: Trivial > Fix For: 0.7.0 > > 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.