[
https://issues.apache.org/jira/browse/CASSANDRA-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-781:
-------------------------------------
Attachment: 781.txt
new patch attached.
> ERROR 06:25:41,032 Internal error processing get_range_slice
added InvalidRequestException when start > end, which fixes this.
> The modified test (below) gets stuck in an infinite loop
Your test is buggy. :)
range_slice (like key_range) is start-INCLUSIVE, so if you pass a key that
exists as start, you will always get at least one result, the start one.
> the keys were not being returned in sorted order
This is working fine for me. Not sure what you were seeing.
> when there are fewer keys in the specified range, duplicates are returned
Sounds like another illustration of start-inclusiveness.
If you still see problems, can you narrow it down to a specific set of keys,
rather than relying on randomness to maybe reproduce it once in a while? That
would help a lot. Thanks!
> in a cluster, get_range_slice() does not return all the keys it should
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-781
> URL: https://issues.apache.org/jira/browse/CASSANDRA-781
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.5
> Environment: Debian 5 lenny on EC2, Gentoo linux, Windows XP
> Reporter: bjc
> Assignee: Jonathan Ellis
> Fix For: 0.5, 0.6
>
> Attachments: 781.txt
>
>
> get_range_slice() does not return the same set of keys as get_key_range() in
> 0.5.0 final.
> I posted a program to reproduce the behavior:
> http://www.mail-archive.com/[email protected]/msg01474.html
> Apparently, you must have more than one node to get the behavior. Also, it
> may depend on the locations of the nodes on the ring.. I.e., if you don't
> generate enough keys randomly, then by chance they could all fall on the same
> host and you might not see the behavior, although I was able to get it to
> happen using only 2 nodes and 10 keys.
> Here are the other emails describing the issue:
> http://www.mail-archive.com/[email protected]/msg02423.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
