You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/01/10 04:28:46 UTC

[jira] Updated: (CASSANDRA-1263) Push replication factor down to the replication strategy

     [ https://issues.apache.org/jira/browse/CASSANDRA-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-1263:
--------------------------------------

    Remaining Estimate: 8h
     Original Estimate: 8h

> 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.8
>
>         Attachments: 1263-incomplete.txt
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> 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.