[
https://issues.apache.org/jira/browse/CASSANDRA-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020724#comment-14020724
]
pankaj mishra commented on CASSANDRA-7311:
------------------------------------------
Yes agreed. There would be too much yamls so keyspace is the the nice place to
handle it.
Now with increasing number of options such as durable_writes,
incremental_backup in keyspace.. should we adopt builder pattern in KSMetaData
as in CFMetaData? Because if we do not then we will have increasing number
arguments in constructor of KSMetaData.
While creating keyspace should this options be mandatory or optional?
> 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
>
>
> 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)
