Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <8035681.17261287696856906.JavaMail.jira@thor>
Date: Thu, 21 Oct 2010 17:34:16 -0400 (EDT)
From: "Jon Hermes (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1263) Push replication factor down to
 the replication strategy
In-Reply-To: <16309702.286341278695090053.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jon Hermes updated CASSANDRA-1263:
----------------------------------

    Attachment: 1263-incomplete.txt

Rep_factor has been wiped off the face of the earth, and the engine for its usage was nicely wrapped up in DD.getReplicationFactor(), so now that just gets the strat for the keyspace and calls strat.getRF().

Converter does the right thing, and the CLI still does the right thing. 

ConfigurationException throwing/handling still needs to be glued onto strategies (most likely in ARS).

The problem right now is that YAML is being finicky, and is either trying to load a map as a non-collection, or it tries to expand the map in place and check for a property on RawKeyspace for every arbitrary strat_opt.

In any event, I'm attaching the partial patch now to make sure it doesn't get lost in the revision-shuffle (and because it's more code than I thought it would be). The best time to finish this may be in a larger YAML/config fix.

> 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
>
>         Attachments: 1263-incomplete.txt
>
>
> 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.