[
https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378789#comment-17378789
]
Aleksei Zotov commented on CASSANDRA-15402:
-------------------------------------------
[~maxwellguo]
Thanks for your interest to the project and providing the initial patch
version! I briefly checked it and I believe you have not yet come up with
another patch version with "configure the table backup under the schema".
Moreover, the patch is quite outdated. Are you still interested (and have
enough time) in continuing this work? If yes, I'd propose to make a kind of
design review: you document the structural changes you're going to make, then
community validates the design, and then you start working on the code. I feel
such a brief design review would be helpful to come up with the best solution
and let you minimize re-work on your side.
If you have no time at the moment (which is totally fine!), let's remove
assignee from the ticket, so someone else could potentially pick it up and
move forward. Anyway, we need to change the status from "PATCH AVAILABLE" to
smth else (IN PROGRESS or OPEN) because it assumes having the patch in the
final stage.
PS:
I'm not a project committer, I'm just an enthusiast like you who is hanging
around the project. I hope I was not rude and discouraging. It is always great
to see people who are ready to dedicate their time to opensource projects.
cc: [~blerer]
> 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.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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
