[
https://issues.apache.org/jira/browse/CASSANDRA-10661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113967#comment-15113967
]
Pavel Yaskevich commented on CASSANDRA-10661:
---------------------------------------------
bq. So is this stuff actually ready to release? I mean, consistent with the new
philosophy that "trunk is always releasable"? IOW, if it does get committed, it
will be in 3.4 no matter what? I only ask because it just seemed that there was
stuff in flux fairly recently (a couple days ago), suggested it wasn't quite
baked enough to be considered "releasable".
Yes, the stuff is ready to release since fairly recently added changes are
ported from 2.0 and clustering support is just couple of lines of additional
filtering added, no internal data structure changes, this is also opt-in
feature which is irrelevant for core functionality until enabled. This is also
the reason why we don't want do any of the CQL front-end related changes right
away but rather more gradual migration.
> 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)
