[ https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979058#comment-16979058 ]
Marcus Eriksson commented on CASSANDRA-15402: --------------------------------------------- yes, this should probably be a table parameter > Make incremental backup configurable per keyspace and table > ----------------------------------------------------------- > > Key: CASSANDRA-15402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15402 > Project: Cassandra > Issue Type: Improvement > Components: Local/Other, Tool/nodetool > Reporter: maxwellguo > Assignee: maxwellguo > Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > We know that when we do backup for cassandra, we can do full bakcup with > snapshot, when we need to backup incremental data , incremental_backup can do > some help . > For snapshot we can just make snapshot for some keyspace/table. but > incremental backup will do all data backup(make hard link for all sstable > that flush from memtable or streaming ). we also know that commitlog's replay > can do some keyspace /table 's filter. > So I think for incremental backup we also need some filter for it.After all > not all keyspace/table is so important to do backup. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org