You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dave Brosius (JIRA)" <ji...@apache.org> on 2016/06/23 05:52:16 UTC
[jira] [Commented] (CASSANDRA-10661) Integrate SASI to Cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-10661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345812#comment-15345812 ]
Dave Brosius commented on CASSANDRA-10661:
------------------------------------------
AbstractTrie.equals isn't symmetric..
someAbstractTrie.equals(someMapEntry) could be true, but
someMapEntry.equals(someAbstractTrie) will always be false.
that is unstable.
> 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.4
>
>
> 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)