[jira] [Commented] (CASSANDRA-11104) KeysSearcher doesn't filter results by key range

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

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

Sylvain Lebresne commented on CASSANDRA-11104:
----------------------------------------------

+1

> KeysSearcher doesn't filter results by key range
> ------------------------------------------------
>
>                 Key: CASSANDRA-11104
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11104
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>             Fix For: 3.0.x, 3.x
>
>
> In 3.0 the check in {{KeysSearcher}} to validate that a hit from the index is falls within the key range of command being executed was ommitted. The effect of this can be observed in a vnode cluster with > 1 node where nodes contain non-contiguous ranges. 
> Because of the lack of range checking, each range command sent to a given replica will return all matching rows, resulting in duplicates in the result set (i.e. one duplicate per merged range).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)