[
https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-15402:
------------------------------------------
Fix Version/s: 4.2
(was: 4.x)
Source Control Link:
https://github.com/apache/cassandra/commit/ee8b66da8ce3bdac0378f89159d8bd7e45a91363
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
thanks everybody, committed here
[https://github.com/apache/cassandra/commit/ee8b66da8ce3bdac0378f89159d8bd7e45a91363]
and dtest modifications here
[https://github.com/apache/cassandra-dtest/commit/e0d3cc90558a17b63634d15ee6df339ceb87b225]
> Make incremental backup configurable per 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: 40m
> 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: [email protected]
For additional commands, e-mail: [email protected]
