[
https://issues.apache.org/jira/browse/CASSANDRA-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200629#comment-13200629
]
Christian Spriegel commented on CASSANDRA-3710:
-----------------------------------------------
Hi Peter,
it is good to know that we are not the only ones having this problem.
The approaches you described are not really suitable for our application. Empty
or old rows would distract the application. Thats why I created a pretty
radical patch for cassandra:
It adds a new config setting called 'test_mode_enabled'. If set to true, it
will disable the commitlog, disable snapshots and disables memtable flushes for
truncates.
I uploaded it, maybe this is useful for your tests too.
Christian
> 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
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
