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

["Erik Onnen (JIRA)" <ji...@apache.org>]

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

Erik Onnen edited comment on CASSANDRA-1126 at 8/6/10 5:56 PM:
---------------------------------------------------------------

So I originally filed this because I'll bootstap multiple instances for debugging from within the same IDE each with a different configuration profile. When working that way, I'm obviously not using bash and I just manually wire in the static portions of the runtime. 

In hindsight, I should have treated the -D value as a URL so that it could be loaded over the network as well as locally which would be even better for our automated deployment.

As another couple of data points, we regularly load log4j.properties with an explicit path to a file (doesn't have to be on the classpath) and both Tomcat and java security policies can be configured w/ absolute file paths that aren't on the classpath.

FWIW, I don't see these as mutually exclusive and the second patch would be an improvement even if mine is rejected.

      was (Author: eonnen):
    So I originally filed this because I'll bootstap multiple instances for debugging from within the same IDE each with a different configuration profile. When working that way, I'm obviously not using bash and I just manually wire in the static portions of the runtime. 

In hindsight, I should have treated the -D value as a URL so that it could be loaded over the network as well as locally which would be even better for our automated deployment.

As another couple of data points, we regularly load log4j.properties with an explicit path to a file (doesn't have to be on the classpath) and both Tomcat and java security policies can be configued w/ absolute file paths that aren't on the classpath.

FWIW, I don't see these as mutually exclusive and the second patch would be an improvement even if mine is rejected.
  
> 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.