[
https://issues.apache.org/jira/browse/CASSANDRA-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830601#action_12830601
]
Jonathan Ellis commented on CASSANDRA-771:
------------------------------------------
> they've changed significantly
take a closer look -- all that's changed is the loop setup using
TM.ringIterator. the loop body is unchanged, except for removing the redundant
foundCount variables.
> Allow range queries against non-primary nodes for a given range
> ---------------------------------------------------------------
>
> Key: CASSANDRA-771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-771
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.6
>
> Attachments:
> 0001-add-TokenMetadata.ringIterator-to-replace-one-offs-of-.txt,
> 0002-iterate-ranges-rather-than-endpoints-and-sort-endpoint.txt
>
>
> Currently any node being down will break range queries that need that node's
> primary range, even if RF > 1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
