cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (Jira)" <>
Subject [jira] [Commented] (CASSANDRA-15402) Make incremental backup configurable per keyspace and table
Date Fri, 30 Jul 2021 12:57:00 GMT


Benjamin Lerer commented on CASSANDRA-15402:

[~maxwellguo] I will put the ticket back to {{OPEN}} until you have the time to work on it
again. Feel frre to change the status to reflect its proper state.

> Make incremental backup configurable per keyspace and table
> -----------------------------------------------------------
>                 Key: CASSANDRA-15402
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message