[CASSANDRA-10765] add RangeIterator interface and QueryPlan for SI

• Type: Sub-task
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Legacy/Local Write-Read Paths
• Labels: 2i sasi
• Assignee: Pavel Yaskevich Assign to me
• Reporter: Pavel Yaskevich

Authors

Pavel Yaskevich

Reviewers

Sam Tunnicliffe

• Created: 23/Nov/15 22:02
• Updated: 07/Mar/23 10:54

Description

Currently built-in indexes have only one way of handling intersections/unions: pick the highest selectivity predicate and filter on other index expressions. This is not always the most efficient approach. Dynamic query planning based on the different index characteristics would be more optimal. Query Plan should be able to choose how to do intersections, unions based on the metadata provided by indexes (returned by RangeIterator) and RangeIterator would became a base for cross index interactions and should have information such as min/max token, estimate number of wrapped tokens etc.

Issue Links

• is depended upon by: CASSANDRA-11734 Enable partition component index for SASI
• relates to: CASSANDRA-12915 SASI: Index intersection with an empty range really inefficient
• supercedes: CASSANDRA-6048 Add the ability to use multiple indexes in a single query