[
https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636138#comment-17636138
]
Stefan Miklosovic commented on CASSANDRA-15402:
-----------------------------------------------
I've run one more CI build as it was some time ago the previous ones were run:
j11 pre-commit:
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1593/workflows/27b6c0b5-df67-4a79-a498-7603f04f2179
j8 pre-commit:
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1593/workflows/a5b01c2c-34f5-4719-b22d-2e178507b2ed
Both jobs included 500x repeat on added test.
> 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.x
>
> 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]
