[
https://issues.apache.org/jira/browse/CASSANDRA-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081283#comment-14081283
]
Brandon Williams commented on CASSANDRA-7311:
---------------------------------------------
I didn't have any strong feeling on this ticket, but realizing that you have to
have a script/app handle the link cleanup anyway, I think the best thing to do
is keep the backups global and let the script/app decide what it wants to
actually back up. The only extra overhead that way is some hardlinks which are
cheap.
> Enable incremental backup on a per-keyspace level
> -------------------------------------------------
>
> Key: CASSANDRA-7311
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7311
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Johnny Miller
> Assignee: pankaj mishra
> Priority: Minor
> Labels: lhf
> Fix For: 2.1.1
>
> Attachments: 7311-cqlsh-update.txt, cassandra-rebased-2.1.patch,
> table_incremental_7311.patch
>
>
> Currently incremental backups are globally defined, however this is not
> always appropriate or required for all keyspaces in a cluster.
> As this is quite expensive, it would be preferred to either specify the
> keyspaces that need this (or exclude the ones that don't).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
