You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "maxwellguo (Jira)" <ji...@apache.org> on 2022/10/28 02:17:00 UTC
[jira] [Updated] (CASSANDRA-15402) Make incremental backup configurable per keyspace and table
[ https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
maxwellguo updated CASSANDRA-15402:
-----------------------------------
Fix Version/s: 4.2
(was: 4.x)
> 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.2
>
> Time Spent: 20m
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org