[
https://issues.apache.org/jira/browse/CASSANDRA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-3453.
---------------------------------------
Resolution: Won't Fix
The complexity I'm referring to is from the user's point of view. Especially
in a cluster setting if you forget to update it on a new machine it can really
cause a head-scratching moment. It doesn't sound like it's worth it to me.
> cassandra.yaml needs a snapshot_directory setting
> -------------------------------------------------
>
> Key: CASSANDRA-3453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3453
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Matthew F. Dennis
>
> cassandra.yaml really needs a config option for a snapshot directory. by
> default it should be a peer folder with saved_caches, commitlog and data.
> assuming the value of that setting is /some/path/snapshot_dir then snapshots
> would go into: /some/path/snapshot_dir/snapshot_name/keyspace_name/
> this makes automation, particularly around backups, much easier and gives
> more control to ops
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
