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

["Jon Hermes (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923092#action_12923092 ] 

Jon Hermes edited comment on CASSANDRA-1263 at 10/20/10 3:04 PM:
-----------------------------------------------------------------

-We need to make sure they give us a replication_factor. We cannot make it required on the def because not all strategies use a static type to give us that information. We should not verify arbitrary key/values in strategy_opts because that is FAR messier than the current solution, and doesn't handle user-created strategies at all.-

All code that asks for RF should really be asking for strategy.getReplicationFactor().

      was (Author: jhermes):
    We need to make sure they give us a replication_factor. We cannot make it required on the def because not all strategies use a static type to give us that information. We should not verify arbitrary key/values in strategy_opts because that is FAR messier than the current solution, and doesn't handle user-created strategies at all.
  
> 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.