cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mck (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10765) add RangeIterator interface and QueryPlan for SI
Date Tue, 03 Apr 2018 00:19:00 GMT


mck commented on CASSANDRA-10765:

[~iksaif], the patch/commit you offered has the shortfall that in {{QueryController.getIndexes(..)}}
the optimization does not take into account the token distribution among index files, and
may miss valid results. I'm no expert on the code in question but I believe this ticket should
remain waiting on a patch along the design that [~xedin] describes above.

> add RangeIterator interface and QueryPlan for SI
> ------------------------------------------------
>                 Key: CASSANDRA-10765
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Local Write-Read Paths
>            Reporter: Pavel Yaskevich
>            Assignee: Pavel Yaskevich
>            Priority: Major
>              Labels: 2i, sasi
>             Fix For: 4.x
>         Attachments: server-load.png
> 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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message