cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1126) Allow loading of cassandra.yaml from a location given on the commandline
Date Thu, 05 Aug 2010 17:09:16 GMT

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

Nick Bailey commented on CASSANDRA-1126:
----------------------------------------

Hmm good point.  

It would still be possible to do it with that patch though. You'd just need a directory for
each conf and to wrap the  call to cassandra with something that sets the conf variable. 


Not quite as easy as the command line I suppose.

> 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.


Mime
View raw message