[
https://issues.apache.org/jira/browse/CASSANDRA-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius updated CASSANDRA-3710:
------------------------------------
Attachment: auto_snapshot_3.diff
sorry, try again... auto_snapshot_3.diff against trunk.
> Add a configuration option to disable snapshots
> -----------------------------------------------
>
> Key: CASSANDRA-3710
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3710
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Brandon Williams
> Assignee: Dave Brosius
> Priority: Minor
> Attachments: Cassandra107Patch_TestModeV1.txt, auto_snapshot.diff,
> auto_snapshot_2.diff, auto_snapshot_3.diff
>
>
> Let me first say, I hate this idea. It gives cassandra the ability to
> permanently delete data at a large scale without any means of recovery.
> However, I've seen this requested multiple times, and it is in fact useful in
> some scenarios, such as when your application is using an embedded cassandra
> instance for testing and need to truncate, which without JNA will timeout
> more often than not.
--
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
