[
https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625384#comment-17625384
]
maxwellguo commented on CASSANDRA-15402:
----------------------------------------
[~blerer] My patch is ready now
[CASSANDRA-15402|https://github.com/Maxwell-Guo/cassandra/tree/CASSANDRA-15402]
.
[CI
|https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra?branch=CASSANDRA-15402]
Can you help to look at this patch ?
and I found it is just like
[CASSANDRA-10383|https://issues.apache.org/jira/browse/CASSANDRA-10383]
[~stefan.miklosovic] can you help to look at this too?
> 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: [email protected]
For additional commands, e-mail: [email protected]
