[jira] Commented: (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:comment-tabpanel&focusedCommentId=12899247#action_12899247 ] Jonathan Ellis commented on CASSANDRA-1126: --- okay, I'm convinced. Sorry about the wait. As an apology I have coded up the URL-based version in v3. (Haven't actually tested it on non-local files though, but it compiles. :) > 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 beta 2 > > Attachments: 1126-v3.txt, 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12901707#action_12901707 ] Jonathan Ellis commented on CASSANDRA-1126: --- Anyone care to review? > 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 >Assignee: Jonathan Ellis >Priority: Trivial > Fix For: 0.7 beta 2 > > Attachments: 1126-v3.txt, 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12901891#action_12901891 ] Gary Dusbabek commented on CASSANDRA-1126: -- +1. alternate locations from within the classpath, remote http:// and local file:// urls all work. Nifty. > 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 >Assignee: Jonathan Ellis >Priority: Trivial > Fix For: 0.7 beta 2 > > Attachments: 1126-v3.txt, 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12901893#action_12901893 ] Gary Dusbabek commented on CASSANDRA-1126: -- I forgot this: you got happy with the imports cleanup. java.lang.reflect.Field needs to go back in. > 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 >Assignee: Jonathan Ellis >Priority: Trivial > Fix For: 0.7 beta 2 > > Attachments: 1126-v3.txt, 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12895730#action_12895730 ] Nick Bailey commented on CASSANDRA-1126: The patch in CASSANDRA-1347 modifies cassandra.in.sh to only modify CASSANDRA_CONF if it is not already set. Not exactly the goal of the title of this ticket but allows for the same result. Personally I don't really see a need for being able to rename the configuration files. > 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12895731#action_12895731 ] Jonathan Ellis commented on CASSANDRA-1126: --- Erik, does that work for you? > 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12895734#action_12895734 ] Gary Dusbabek commented on CASSANDRA-1126: -- >Personally I don't really see a need for being able to rename the >configuration files. It's very handy from a development perspective when you're running multiple instances on a single machine. > 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.
[jira] Commented: (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: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.
[jira] Commented: (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: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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12896171#action_12896171 ] Erik Onnen commented on CASSANDRA-1126: --- 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.
