[
https://issues.apache.org/jira/browse/CASSANDRA-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037259#comment-13037259
]
Hudson commented on CASSANDRA-2592:
-----------------------------------
Integrated in Cassandra-0.8 #119 (See
[https://builds.apache.org/hudson/job/Cassandra-0.8/119/])
properly handle empty result set
Patch by Pavel Yaskevich; reviewed by eevans for CASSANDRA-2592
eevans : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1125622
Files :
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cql/QueryProcessor.java
> 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
