[
https://issues.apache.org/jira/browse/CASSANDRA-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050572#comment-13050572
]
Jonathan Ellis commented on CASSANDRA-2369:
-------------------------------------------
bq. There is a similar problem on bootstrap and node movement. Instead of
asking a single replica to stream data from the range a new node is assuming,
it will have to ask all replicas that may have rows for that range to make sure
it doesn't miss any.
Additionally, each source replica would have to deserialize each row in the
range to make sure it's actually supposed to be streamed, which would slow
streaming down significantly.
Starting to think this is not worth trying to support.
> 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: Vijay
> 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
