[ https://issues.apache.org/jira/browse/CASSANDRA-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923104#action_12923104 ]
Jonathan Ellis commented on CASSANDRA-1263: ------------------------------------------- bq. the only references to [RF] outside the Strategy classes themselves are a couple assert statements that could easily be cleaned up. [reply-to-self] Actually I don't think this is true, wanting to know the total number of copies of the data is a reasonable thing to do. bq. All code that asks for RF should really be asking for strategy.getReplicationFactor(). Agreed. > Push replication factor down to the replication strategy > -------------------------------------------------------- > > Key: CASSANDRA-1263 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1263 > Project: Cassandra > Issue Type: Task > Components: Core > Reporter: Jeremy Hanna > Assignee: Jon Hermes > Priority: Minor > Fix For: 0.7.0 > > > Currently the replication factor is in the keyspace metadata. As we've added > the datacenter shard strategy, the replication factor becomes more computed > by the replication strategy. It seems reasonable to therefore push the > replication factor for the keyspace down to the replication strategy so that > it can be handled in one place. > This adds on the work being done in CASSANDRA-1066 since that ticket will > make the replication strategy a member variable of keyspace metadata instead > of just a quasi singleton giving the replication strategy state for each > keyspace. That makes it able to have the replication factor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.