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/04/12 20:04:05 UTC
[jira] [Assigned] (CASSANDRA-2369) support replication decisions
per-key
[ https://issues.apache.org/jira/browse/CASSANDRA-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-2369:
-----------------------------------------
Assignee: paul cannon (was: Jonathan Ellis)
I think the goal here is to end up with AbstractReplicationStrategy.getNaturalEndpoints take a DecoratedKey parameter instead of a Token.
Ultimately, even assuming that we always start by decorating the key with a token might be assuming too much (and want to decide based on the raw ByteBuffer key) but let's not borrow trouble; it should be a lot easier to make the DecoratedKey change since existing code that wants a token can easily be satisfied that way.
> support replication decisions per-key
> -------------------------------------
>
> Key: CASSANDRA-2369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2369
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: paul cannon
> Priority: Minor
> Fix For: 1.0
>
>
> Currently the replicationstrategy gets a token and a keyspace with which to decide how to place replicas. for per-row replication this is insufficient because tokenization is lossy (CASSANDRA-1034).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira