[
https://issues.apache.org/jira/browse/CASSANDRA-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037107#comment-13037107
]
Jonathan Ellis commented on CASSANDRA-2592:
-------------------------------------------
I think Pavel's patch is more correct since the result could come back with
exactly one row equal to the start key on a "KEY > X AND KEY < Y" query. Then
we want to remove the extra row on the first check, w/o erroring out on the
second.
> 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
>
> Attachments: 2592-v3-in-progress.txt,
> CASSANDRA-2592-fix-when-rows-are-empty.patch, CASSANDRA-2592-v2.patch,
> CASSANDRA-2592-v3.patch, CASSANDRA-2592.patch,
> v1-0001-CASSANDRA-2592-handle-empty-result-sets.txt
>
>
> 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
