[
https://issues.apache.org/jira/browse/CASSANDRA-10765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378193#comment-16378193
]
Corentin Chary commented on CASSANDRA-10765:
--------------------------------------------
Note: after having troubles like this with SASI, we ended moving to
[https://github.com/Stratio/stratio-cassandra.] IMHO leveraging lucene instead
of building yet another index makes much more sense. Would be great to see SASI
using Lucene internally (even if it's somewhat against the current design).
Before using stratio we starting experimenting with a SASI-Like Lucene enabled
index, see https://github.com/criteo/biggraphite/tree/master/tools/graphiteindex
> 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
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
