[
https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733913#action_12733913
]
Jonathan Ellis commented on CASSANDRA-212:
------------------------------------------
> When moving to the next node, you want to be careful not to pick up
> duplicated keys.
that is why you give the last value received from node #1 as the start_with
parameter to node #2. so at most there will be one duplicate.
> Sometimes, it is more efficient to scan multiple nodes in parallel
Unless you have trivially small amounts of data on each node, in which case it
doesn't matter, any number that's going to fit in memory is going to be better
served by sequential scanning since the odds are excellent that you won't have
to cross to another node.
> Range queries do not yet span multiple nodes
> --------------------------------------------
>
> Key: CASSANDRA-212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-212
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Fix For: 0.4
>
>
> Need ability to continue a query on the next node in the ring, if necessary
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
