You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (JIRA)" <ji...@apache.org> on 2016/05/05 20:01:12 UTC

[jira] [Created] (CASSANDRA-11721) Have a per operation truncate ddl "no snapshot" option

Jeremy Hanna created CASSANDRA-11721:
----------------------------------------

             Summary: Have a per operation truncate ddl "no snapshot" option
                 Key: CASSANDRA-11721
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11721
             Project: Cassandra
          Issue Type: Wish
          Components: CQL
            Reporter: Jeremy Hanna
            Priority: Minor


Right now with truncate, it will always create a snapshot.  That is the right thing to do most of the time.  'auto_snapshot' exists as an option to disable that but it is server wide and requires a restart to change.  There are data models, however, that require rotating through a handful of tables and periodically truncating them.  Currently you either have to operate with no safety net (some actually do this) or manually clear those snapshots out periodically.  Both are less than optimal.

In HDFS, you generally delete something where it goes to the trash.  If you don't want that safety net, you can do something like 'rm -rf -skiptrash /jeremy/stuff' in one command.

It would be nice to have something in the truncate ddl to skip the snapshot on a per operation basis.  Perhaps 'TRUNCATE solarsystem.earth NO SNAPSHOT'.

This might also be useful in those situations where you're just playing with data and you don't want something to take a snapshot in a development system.  If that's the case, this would also be useful for the DROP operation, but that convenience is not the main reason for this option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)