cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pankaj mishra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7311) Enable incremental backup on a per-keyspace level
Date Thu, 19 Jun 2014 02:53:25 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036884#comment-14036884
] 

pankaj mishra commented on CASSANDRA-7311:
------------------------------------------

I only  one line change in cassandra.thrift. Rest are auto generated file.

There are so many changes in KsDef.java because the version of thrift changed.

Actually As i can see from history of KsDef.java,
 in commit "bffd9ea8eb5358b5f138cbad8a387d5037d1ac12" it was upgraded to thrift version 0.9.1
but then after that in
commit "5c0c84b3d115880e786063df3b6e5f59eff402a0" it was reverted back to 0.7.0. If this file
would have been on thrift version  0.9.1 then there would not be so many changes.




> 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
>
>
> 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)

Mime
View raw message