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:13:16 GMT

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

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

Actually you could just do:

> CASSANDRA_CONF='path/to/conf' bin/cassandra

for each call. Not really that diffrent than -Dcassandra.conf

> 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