[CASSANDRA-1600] Merge get_indexed_slices with get_range_slices

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: Legacy/CQL
• Assignee: Sylvain Lebresne
• Reporter: Stu Hood

Authors

Sylvain Lebresne

Reviewers

Jonathan Ellis

• Created: 11/Oct/10 02:41
• Updated: 16/Apr/19 09:33
• Resolved: 02/Jan/12 16:35

Description

From a comment on 1157:

IndexClause only has a start key for get_indexed_slices, but it would seem that the reasoning behind using 'KeyRange' for get_range_slices applies there as well, since if you know the range you care about in the primary index, you don't want to continue scanning until you exhaust 'count' (or the cluster).

Since it would appear that get_indexed_slices would benefit from a KeyRange, why not smash get_(range|indexed)_slices together, and make IndexClause an optional field on KeyRange?

Issue Links

• blocks: CASSANDRA-2878 Allow map/reduce to use server-side query filters
• blocks: CASSANDRA-2246 Enable Pig to use indexed data as described in CASSANDRA-2245
• is blocked by: CASSANDRA-1034 Remove assumption that Key to Token is one-to-one
• is related to: CASSANDRA-2601 should have a get_indexed_slices count api