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 2009/06/03 11:24:07 UTC
[jira] Created: (CASSANDRA-212) Range queries do not yet span
multiple nodes
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
Reporter: Jonathan Ellis
Assignee: 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736981#action_12736981 ]
Arin Sarkissian commented on CASSANDRA-212:
-------------------------------------------
i thought about the HashMap thing but Sammy and I thought that was kinda hacky. I'll see about merging RangeResult with RangeReply.
I'll have some alternative(s) tomorrow.
Also - i have no problem renaming the boolean. rangeCompletedLocally sounds most descriptive to me so ill go with that
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-Cassandra-212.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735899#action_12735899 ]
Jonathan Ellis commented on CASSANDRA-212:
------------------------------------------
looks good, modulo the headers being in all the diffs (whitespace?)
> still need to work on the replicas
all you need to do is change
command = new RangeCommand(command.table, command.columnFamily, command.startWith, command.stopAt, command.maxResults - rangeKeys.size());
to pass in the last key from the previous node as the start. right? or are you talking about something else?
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725775#action_12725775 ]
Jonathan Ellis commented on CASSANDRA-212:
------------------------------------------
All this needs is a bool added to RangeReply that is true if it stopped b/c the next local key was not part of the range, or the asked-for limit was reached.
If a reply comes back with that bool false, then the coordinator node, the one talking to the client, sends the query to the next node in the ring down from the one it just got a reply from and appends those results to the list it's going to return to the client.
Repeat until the i'm-done-bool comes back true.
> 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
> Reporter: Jonathan Ellis
> Assignee: 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736887#action_12736887 ]
Arin Sarkissian commented on CASSANDRA-212:
-------------------------------------------
created an object called RangeResult that encapsulates the keys and a boolean flag called isInRange.
i plumbed this thru RangeReply and to StorageProxy.getKeyRange
there's a squashed commit with all changes at:
http://github.com/phatduckk/Cassandra/commit/a5b2d264a1567a97b04e6d7874e0114a3ebd32d8
is the RangeResult stuff ok? It seemed to be the best way to flag whether a node had gone thru its entire range or not
(ignore ws diff - i'll prune those when i make a patch)
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-Cassandra-212.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736968#action_12736968 ]
Jonathan Ellis commented on CASSANDRA-212:
------------------------------------------
Looks good to me overall.
RangeResult looks an awful lot like RangeReply w/ less methods. Could we just use RangeReply and cut out the middleman? I dunno. Java feels so clunky here.
One way to return multiple values would be like this
return new HashMap<String, Object>() {{
put("keys", listOfStrings);
put("finished", true);
}};
Who says constructor blocks aren't useful? :)
Can we the bool in RangeReply it something besides isInRange? In the range does not imply "contains the entire range" to me. Rather the opposite relationship. If you don't like "finished" maybe isComplete, rangeComplete, rangeCompletedLocally, ...
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-Cassandra-212.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736426#action_12736426 ]
Jonathan Ellis commented on CASSANDRA-212:
------------------------------------------
i'm a little confused by the git commit message.
which of those are "mission accomplished" and which are "to-dos" if any? :)
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-Cassandra-212.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arin Sarkissian updated CASSANDRA-212:
--------------------------------------
Attachment: 0001-All-patches-for-212.-All-comments-in-https-issues.patch
single patch file to address the range queries
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-All-patches-for-212.-All-comments-in-https-issues.patch, 0001-Cassandra-212.patch
>
>
> 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.
[jira] Assigned: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-212:
----------------------------------------
Assignee: (was: Jonathan Ellis)
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737565#action_12737565 ]
Jonathan Ellis commented on CASSANDRA-212:
------------------------------------------
does not apply to trunk (because of CASSANDRA-111 maybe?), can you rebase?
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-All-patches-for-212.-All-comments-in-https-issues.patch, 0001-Cassandra-212.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733896#action_12733896 ]
Jun Rao commented on CASSANDRA-212:
-----------------------------------
This can be a bit tricky because the key ranges btw 2 consecutive nodes overlap (because of replication). When moving to the next node, you want to be careful not to pick up duplicated keys.
Also, the approach that Jonathan described forces nodes to be scanned sequentially. Sometimes, it is more efficient to scan multiple nodes in parallel, especially if maxResult is unspecified.
> 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.
[jira] Updated: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arin Sarkissian updated CASSANDRA-212:
--------------------------------------
Attachment: 0001-All-patches-for-212.-All-comments-in-https-issues.patch
new patch with previous comments addressed
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-All-patches-for-212.-All-comments-in-https-issues.patch, 0001-Cassandra-212.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737874#action_12737874 ]
Hudson commented on CASSANDRA-212:
----------------------------------
Integrated in Cassandra #154 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/154/])
Make range queries continue on the next node when necessary.
Patch by Arin Sarkissian; reviewed by jbellis for
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-All-patches-for-212.-All-comments-in-https-issues.patch, 0001-Cassandra-212.patch, rebased-212-against-9164940f41972e3611d1ad38a903ca39562e6feb.patch
>
>
> 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.
[jira] Assigned: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arin Sarkissian reassigned CASSANDRA-212:
-----------------------------------------
Assignee: Arin Sarkissian
> 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
> Assignee: Arin Sarkissian
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736429#action_12736429 ]
Jonathan Ellis commented on CASSANDRA-212:
------------------------------------------
we still need this part
> this needs a bool added to RangeReply that is true if it stopped b/c the next local key was not part of the range, or the asked-for limit was reached
otherwise we have to do extra queries for every range command that doesn't hit the max results or the end key.
also,
while (endPoint != null)
if (endPoint.toString().equals(firstEndpoint)) break
these seem redundant, shouldn't it be while (true) if (endpoint == null) { throw } ?
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-Cassandra-212.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733875#action_12733875 ]
Jonathan Ellis commented on CASSANDRA-212:
------------------------------------------
(the relevant starting point is StorageProxy.getKeyRange)
> 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.
[jira] Updated: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arin Sarkissian updated CASSANDRA-212:
--------------------------------------
Attachment: rebased-212-against-9164940f41972e3611d1ad38a903ca39562e6feb.patch
rabased my last patch against trunk @ 9164940f41972e3611d1ad38a903ca39562e6feb
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-All-patches-for-212.-All-comments-in-https-issues.patch, 0001-Cassandra-212.patch, rebased-212-against-9164940f41972e3611d1ad38a903ca39562e6feb.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arin Sarkissian updated CASSANDRA-212:
--------------------------------------
Attachment: 0001-Cassandra-212.patch
attempt at #212
unit tests and nosetests pass
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-Cassandra-212.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Mark Robson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730887#action_12730887 ]
Mark Robson commented on CASSANDRA-212:
---------------------------------------
Sounds like a pretty serious bug in the general case, but might not happen very often in practice.
> 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
> Reporter: Jonathan Ellis
> Assignee: 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.
[jira] Commented: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735873#action_12735873 ]
Arin Sarkissian commented on CASSANDRA-212:
-------------------------------------------
first cut at http://github.com/phatduckk/Cassandra/commit/b535b00f2917995f93f5838a98e08931e2b52680
I did a bunch of refactoring to get a lot of the get*Endpoint*() type methods to take an offset.
still need to work on the replicas.
anyways... wanted feedback on the approach. anyone wanna take a look and lemme know what you think?
> 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.
[jira] Updated: (CASSANDRA-212) Range queries do not yet span
multiple nodes
Posted by "Arin Sarkissian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arin Sarkissian updated CASSANDRA-212:
--------------------------------------
Attachment: (was: 0001-All-patches-for-212.-All-comments-in-https-issues.patch)
> 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
> Assignee: Arin Sarkissian
> Fix For: 0.4
>
> Attachments: 0001-Cassandra-212.patch
>
>
> 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.