[ 
https://issues.apache.org/jira/browse/CASSANDRA-11721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Lerer updated CASSANDRA-11721:
---------------------------------------
    Description: 
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.

+Additional information for newcomers:+

The idea is to support disabling snapshots when performing a Truncate as follow:
 



  was:
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.

+Additional information for newcomers:+




> 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: Improvement
>          Components: Legacy/CQL
>            Reporter: Jeremy Hanna
>            Priority: Low
>
> 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.
> +Additional information for newcomers:+
> The idea is to support disabling snapshots when performing a Truncate as 
> follow:
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to