[
https://issues.apache.org/jira/browse/CASSANDRA-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038752#comment-14038752
]
pankaj mishra commented on CASSANDRA-7311:
------------------------------------------
I think giving option for incremental backup on table level will definitely
give user more flexibility. But
there are some application, for example when using cassandra with titan graph,
tables in keyspace are
depended on each other. They refer other table through ids. In that case it
does not make sense to have
incremental backup on table level.
How much users of cassandra has such setup of cassandra is something that, i
think, will decide whether
this option should be on table level or keyspace level.
If you guys suggest then i can go ahead with creating this option for table
level as well.
> 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
> Priority: Minor
> Labels: lhf
> Attachments: CASSANDRA-7311-formated.patch, cassandra.patch,
> cassandra_incremental.patch, cassandra_incremental_latest.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)
