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 2011/05/04 23:53:03 UTC

[jira] [Issue Comment Edited] (CASSANDRA-2592) CQL greater-than and less-than operators (> and <) result in key ranges that are inclusive of the terms

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

Jonathan Ellis edited comment on CASSANDRA-2592 at 5/4/11 9:52 PM:
-------------------------------------------------------------------

I think this patch makes it so if I say "LIMIT 10" I might only get 8 back because one result got chopped off.  QP will need to request more than LIMIT to give back the right number.

Can you add a test for this?

      was (Author: jbellis):
    I think this patch makes it so if I say "LIMIT 100" I might only get 98 back because one result got chopped off.  QP will need to request more than LIMIT to give back the right number.
  
> CQL greater-than and less-than operators (> and <) result in key ranges that are inclusive of the terms
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2592
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2592
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.8 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>             Fix For: 0.8.0 beta 2
>
>         Attachments: CASSANDRA-2592.patch
>
>
> This affects range queries against keys, but not index queries.
> One possible solution: let the coordinator strip out the extra row in QueryProcessor.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira