cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-763) getRangeSlice returns keys from outside the desired range
Date Fri, 05 Feb 2010 20:06:28 GMT


Jonathan Ellis commented on CASSANDRA-763:

the semantics of client start/end keys passed to get_range_slice and the tokens in a Range
object are different.  CASSANDRA-759 and CASSANDRA-758 tried to add options to getRangeSlice
to be able to handle both but the two are still too different.  consider for instance the
case where start=end -- in the former case this is a range with exactly one (potential) key
included; in the latter it is a wrapping range including the entire ring.

this partially backs out 758 and 759 and instead adds a Bounds class (that shares a common
superclass w/ Range); getRangeSlice can then take either a Bounds (which has the semantics
of the old start/end pair) or a Range, which is the case CASSANDRA-342 is interested in, and
can now use intersectsWith to make sure we're only getting each key once.

> getRangeSlice returns keys from outside the desired range
> ---------------------------------------------------------
>                 Key: CASSANDRA-763
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.6
>         Attachments: 0001-add-Range.intersectsWith.txt, 0002-have-RangeSliceCommand-take-Range-or-Bounds-client-bou.txt

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message