You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2015/12/02 04:09:11 UTC

[jira] [Commented] (CASSANDRA-10765) add RangeIterator interface and QueryPlan for SI

    [ https://issues.apache.org/jira/browse/CASSANDRA-10765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035184#comment-15035184 ] 

Pavel Yaskevich commented on CASSANDRA-10765:
---------------------------------------------

After working on this for a couple of days it looks like this is going to require a bunch of changes to the existing SI API, so instead we are planing to take an alternative route: merge SASI with trunk as is; add composite support and merge SASI into trunk, after doing that we can try to incrementally integrate it with the existing indexes.

> add RangeIterator interface and QueryPlan for SI
> ------------------------------------------------
>
>                 Key: CASSANDRA-10765
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10765
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Local Write-Read Paths
>            Reporter: Pavel Yaskevich
>            Assignee: Pavel Yaskevich
>             Fix For: 3.2
>
>
> 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
(v6.3.4#6332)