cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3710) Add a configuration option to disable snapshots
Date Mon, 02 Apr 2012 20:27:25 GMT


Jonathan Ellis updated CASSANDRA-3710:

    Fix Version/s:     (was: 1.0.10)

I'm fine with adding an autosnapshot configuration variable defaulting to true that controls
whether to snapshot before truncate and drop.
> Add a configuration option to disable snapshots
> -----------------------------------------------
>                 Key: CASSANDRA-3710
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Brandon Williams
>            Priority: Minor
>         Attachments: Cassandra107Patch_TestModeV1.txt
> 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:!default.jspa
For more information on JIRA, see:


View raw message