[
https://issues.apache.org/jira/browse/CASSANDRA-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887248#action_12887248
]
Jonathan Ellis commented on CASSANDRA-1126:
-------------------------------------------
I still feel like this is the Wrong Solution, given that log4j, datacenter
properties, and snitch properties all still load from classpath.
What about an option for bin/cassandra.in.sh to override CASSANDRA_CONF
variable?
> 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.
