[CASSANDRA-11104] KeysSearcher doesn't filter results by key range

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.3, 3.3
• Component/s: Legacy/Local Write-Read Paths
• Severity: Normal
• Since Version: 3.0 alpha 1
• Assignee: Sam Tunnicliffe
• Reporter: Sam Tunnicliffe

Authors

Sam Tunnicliffe

• Created: 01/Feb/16 20:59
• Updated: 16/Apr/19 09:30
• Resolved: 02/Feb/16 15:50

Description

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).