cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10661) Integrate SASI to Cassandra
Date Tue, 22 Dec 2015 01:46:47 GMT


Pavel Yaskevich commented on CASSANDRA-10661:

[~beobal] Here is the latest status: I've attempted to integrate OR/Parenthesis into the CQL3
and SelectStatement which, as I've figured, actually would still require CASSADRA-10765 to
be implemented since all of the restrictions have to be constructed/checked per logical operation
(in other words, per CQL3 statement we'll have to build operation graph instead of current
list approach) which would require substantial changes in SelectStatement, StatementRestrictions
and other query processing classes. Maybe an alternative, and granular approach, would be
more appropriate in this case:

phase #1 - SASI goes into trunk supporting AND only (in other words, having QueryPlan internalized,
no changes to CQL3);
phase #2 - implement CASSANDRA-10765 with AND support only, which would supersede restriction
support (via StatementRestrictions) in CQL3;
phase #3 - add OR support to, by that time, already global QueryPlan.


> Integrate SASI to Cassandra
> ---------------------------
>                 Key: CASSANDRA-10661
>                 URL:
>             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 (
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|],
into mainline Cassandra 3.x release.

This message was sent by Atlassian JIRA

View raw message