[
https://issues.apache.org/jira/browse/CASSANDRA-10661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113842#comment-15113842
]
Jon Haddad edited comment on CASSANDRA-10661 at 1/23/16 5:02 PM:
-----------------------------------------------------------------
If sparse means what Jack is implying, perhaps a better name for it would be
EXACT.
Using SPARSE will usually result in people asking "what does that mean", and
the answer will be "exact match" so I propose we just use that as it'll cut
down on the number of questions people have.
was (Author: rustyrazorblade):
If sparse means what Jack is implying, perhaps a better name for it would be
EXACT
> 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)
