cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5573) Querying with an empty (impossible) range returns incorrect results
Date Thu, 16 May 2013 20:09:16 GMT

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

Alex Liu commented on CASSANDRA-5573:
-------------------------------------

 * The semantics of start keys and tokens are slightly different.
 * Keys are start-inclusive; tokens are start-exclusive.  Token
 * ranges may also wrap -- that is, the end token may be less
 * than the start one.  Thus, a range from keyX to keyX is a
 * one-element range, but a range from tokenY to tokenY is the
 * full ring.

So that query covers the whole ring. I think it's a bug in the hadoop code. I will fix it
in CASSANDRA-4421
                
> Querying with an empty (impossible) range returns incorrect results
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-5573
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5573
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.4
>            Reporter: Mike Schrag
>
> SELECT * FROM cf WHERE token(key) > 2000 AND token(key) <= 2000 LIMIT 1000 ALLOW
FILTERING;
> This should return nothing, but instead appears to freak and return arbitrary token values.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message