cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pankaj mishra (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7311) Enable incremental backup on a per-keyspace level
Date Fri, 20 Jun 2014 13:31:25 GMT


pankaj mishra commented on CASSANDRA-7311:

So finally going for following implementation.

 - If table is created without incremental_backup option then by default this value will be
saved as false in table metadata. This value will be alterable by user.

- For all those tables in which this value is not there (as null) we will pick incremental_backup
options from cassandra.yaml and save it into table metadata while initializing the cassandra
server.  -- hence one who is using this option in cassandra.yaml file will be taken care of.

> Enable incremental backup on a per-keyspace level
> -------------------------------------------------
>                 Key: CASSANDRA-7311
>                 URL:
>             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

View raw message