[
https://issues.apache.org/jira/browse/CASSANDRA-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797152#action_12797152
]
Gary Dusbabek commented on CASSANDRA-620:
-----------------------------------------
My thoughts here are to push the replication factor down into the replication
strategy (where it exists in the code already), and then push the replication
strategy down into the keyspace.
I don't think we can easily do the replication factor without bringing in
table-specific replication strategies as well, simply for the reason that the
AbstractReplicationStrategy member of the StorageService singleton no longer
makes sense.
> Add per-keyspace replication factor (possibly even replication strategy)
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-620
> URL: https://issues.apache.org/jira/browse/CASSANDRA-620
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Fix For: 0.9
>
>
> (but partitioner may only be cluster-wide, still)
> not 100% sure this makes sense but it would allow maintaining system metadata
> in a replicated-across-entire-cluster keyspace (without ugly special casing),
> as well as making Cassandra more flexible as a shared resource for multiple
> apps
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
