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 (Commented) (JIRA)" <ji...@apache.org> on 2012/01/19 15:58:43 UTC

[jira] [Commented] (CASSANDRA-3749) Allow rangeSlice queries to be start/end inclusive/exclusive

    [ https://issues.apache.org/jira/browse/CASSANDRA-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189141#comment-13189141 ] 

Jonathan Ellis commented on CASSANDRA-3749:
-------------------------------------------

+1
                
> Allow rangeSlice queries to be start/end inclusive/exclusive 
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-3749
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3749
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 1.1
>
>         Attachments: 3749-comments.txt, 3749-v2.patch, 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira