cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3749) Allow rangeSlice queries to be start/end inclusive/exclusive
Date Wed, 18 Jan 2012 22:06:41 GMT


Jonathan Ellis updated CASSANDRA-3749:

    Attachment: 3749-comments.txt

Even after updating the comments to make things a bit more clear (attached), I'm still confused
by the remainder/split dance.  For instance, if we are splitting a Bounds on bounds.right,
that means that remainder overlaps Bounds entirely and so we should add that to the ranges,
but instead we skip it.
> Allow rangeSlice queries to be start/end inclusive/exclusive 
> -------------------------------------------------------------
>                 Key: CASSANDRA-3749
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 1.1
>         Attachments: 3749-comments.txt, 3749.patch
> Currently, given two keys k1 and k2, we can only do a rangeSlice on the intervals (k1,
k2] (Range) and [k1, k2] (Bounds). CQL goes around this "manually", by querying one more row
if the start is exclusive and removing the start/end post-query if necessary. This doesn't
work however with the new option introduced by CASSANDRA-3742. So this ticket proposes to
add support (internally) for doing a rangeSlice for the intervals (k1, k2) an [k1, k2).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message