[
https://issues.apache.org/jira/browse/CASSANDRA-10765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238357#comment-15238357
]
Pavel Yaskevich commented on CASSANDRA-10765:
---------------------------------------------
[~doanduyhai] Yes, most likely, one of the goals here to be able to use
different index implementations in a single query efficiently e.g. use built-in
composite index as iterator and check for intersections inside of SASI index
for precision before reading row from primary storage.
> 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.x
>
>
> 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)
