cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-2369) support replication decisions per-key
Date Tue, 12 Apr 2011 18:04:05 GMT

     [ 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

Mime
View raw message