[
https://issues.apache.org/jira/browse/CASSANDRA-10661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111582#comment-15111582
]
Pavel Yaskevich commented on CASSANDRA-10661:
---------------------------------------------
[~beobal] Thinking more about it, we should probably proceed with
implementation of the clustering that I've finished last night to conclude
phase #1, since it's already an improvement over internal indexes anyway and it
would take some time to have TokenTree keys with flexible size implemented
which is going to speed up intersections but not necessarily satisfies-by at
the end of the query, so benefit of it is uncertain at this point, because we
have to scan through all row clusters anyway. So let's prioritize phase #2 and
#3 over that for now, WDYT?
P.S. I have been running testall and dtest in CI (0 failures for testall, some
old failures for dtest):
||branch||testall||dtest||
|[sasi-integration|https://github.com/xedin/sasi/]|[testall|http://cassci.datastax.com/job/xedin-sasi-3.2-integration-testall/]|[dtest|http://cassci.datastax.com/job/xedin-sasi-3.2-integration-dtest/]|
> Integrate SASI to Cassandra
> ---------------------------
>
> Key: CASSANDRA-10661
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10661
> Project: Cassandra
> Issue Type: Improvement
> Components: Local Write-Read Paths
> Reporter: Pavel Yaskevich
> Assignee: Pavel Yaskevich
> Labels: sasi
> Fix For: 3.x
>
>
> We have recently released new secondary index engine
> (https://github.com/xedin/sasi) build using SecondaryIndex API, there are
> still couple of things to work out regarding 3.x since it's currently
> targeted on 2.0 released. I want to make this an umbrella issue to all of the
> things related to integration of SASI, which are also tracked in
> [sasi_issues|https://github.com/xedin/sasi/issues], into mainline Cassandra
> 3.x release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
