You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/07/12 06:42:50 UTC

[jira] Updated: (CASSANDRA-1126) Allow loading of cassandra.yaml from a location given on the commandline

     [ https://issues.apache.org/jira/browse/CASSANDRA-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-1126:
--------------------------------------

    Summary: Allow loading of cassandra.yaml from a location given on the commandline  (was: Allow loading of cassandra.yaml from a location off the classpath)

Updated issue subject since apparently that is a hurdle here.

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