[
https://issues.apache.org/jira/browse/CASSANDRA-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193928#comment-13193928
]
Christian Spriegel commented on CASSANDRA-3710:
-----------------------------------------------
I think I came up with a real use case for this: It would be useful for
Development or Quality Systems. I personally dont care if data gets lost on my
Development machines. But I dont like deleting snapshots on all those machines.
Afaik also schema updates create snapshots.
Jonathan: Would it help if somebody would provide a patch for this, or are you
against it?
> 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
> Fix For: 1.0.8
>
>
> 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
