You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2013/07/12 15:18:00 UTC
[jira] [Commented] (CASSANDRA-5573) Querying with an empty
(impossible) range returns incorrect results
[ https://issues.apache.org/jira/browse/CASSANDRA-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706927#comment-13706927 ]
Aleksey Yeschenko commented on CASSANDRA-5573:
----------------------------------------------
LGTM, +1
nanonits:
- you can kill both ColumnSlice.validate() overloads (only used by QP.validateSLiceFilter) altogether if you ditch QueryProcessor.validateSliceFilter() (unused).
- SelectStatement.getKeyBounds() comment 'it will happilly return the whole' has a typo in 'happilly'.
> 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
> Assignee: Sylvain Lebresne
> Fix For: 1.2.7
>
> Attachments: 5573.txt
>
>
> 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