[
https://issues.apache.org/jira/browse/CASSANDRA-10661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112458#comment-15112458
]
Sam Tunnicliffe commented on CASSANDRA-10661:
---------------------------------------------
bq. So let's prioritize phase #2 and #3 over that for now, WDYT?
Sounds good to me. I've only one tiny comment about the latest commits, which
is that it's slightly odd API-wise that {{SSTableFlushObserver::nextRow}} takes
an {{Unfiltered}} rather than a {{Row}}. Maybe renaming it to
{{nextUnfiltered}} or even just {{flushed}} would make sense.
> 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)
