[
https://issues.apache.org/jira/browse/CASSANDRA-10661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119962#comment-15119962
]
DOAN DuyHai commented on CASSANDRA-10661:
-----------------------------------------
Last but not least. We have an use-case for secondary index that is pretty
interesting. With the *Spark/Cassandra* connector, since each Spark partition
is distributed according to Cassandra token ranges, each CQL query is *node
local*.
Consequently a
{code:sql}
SELECT * FROM table WHERe col=xxx`
{code}
is transformed by the connector into
{code:sql}
SELECT * FROM table WHERE col=xxx AND token(pk)>=aaa AND token(pk) <= bbb
{code}
The normal CQL query engine is token-aware and will restrict the secondary
index query on the given range. *Does SASI query planner also take into account
token range restrictions to avoid hitting un-necessary nodes ?*
> 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)
