[
https://issues.apache.org/jira/browse/CASSANDRA-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870949#action_12870949
]
Erik Onnen commented on CASSANDRA-1126:
---------------------------------------
Most of those files though are unlikely to change across deployments I think
(I'm not likely to have a different passwd.properties across nodes for example)
and I can already override log4j with a -D property. cassandra.yaml is the most
likely to have host-specific configurations. From an automation perspective
then, I have to drop the tar.gz, expand, then process cassandra.yaml. Not a big
deal, but I'd rather have the ability to keep the parts that are host-specific
outside the classpath and the static tar.gz that lays everything down when
provisioning out a new host. It's easier to upgrade that way, easier to use an
IDS, easier to backup, etc.
As another example, we run an embedded server in our functional tests with
temporary data and commit dirs created at runtime. Because the config has to be
on the classpath, I have to get a cassandra.yaml config on the test classpath,
load and process it before starting the embedded server. I'd rather just write
out my new config file to the same temporary directory as my logs and datafiles
and point the embedded server at that.
Again, not a big deal at all but it's already made my automation noticeably
easier.
> 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.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.
