[CASSANDRA-4858] Coverage analysis for low-CL queries

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.2.1
• Assignee: Sylvain Lebresne
• Reporter: Jonathan Ellis

Authors

Sylvain Lebresne

Reviewers

Vijay

• Created: 24/Oct/12 21:25
• Updated: 16/Apr/19 09:32
• Resolved: 18/Jan/13 14:20

Description

There are many cases where getRangeSlice creates more
RangeSliceCommand than it should, because it always creates one for each range
returned by getRestrictedRange. Especially for CL.ONE this does not take
the replication factor into account and is potentially pretty wasteful.
A range slice at CL.ONE on a 3 node cluster with RF=3 should only
ever create one RangeSliceCommand.

Issue Links

• relates to: CASSANDRA-1337 parallelize fetching rows for low-cardinality indexes and range scans of small tables