[
https://issues.apache.org/jira/browse/CASSANDRA-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399144#comment-15399144
]
Sylvain Lebresne commented on CASSANDRA-11990:
----------------------------------------------
I'm not familiar enough with the SASI code at this point to have much opinions
on the specifics of what is the best implementation choices. But it does sound
like supporting other partitioners is fairly orthogonal to the original ticket
intent so it should likely be left to a follow-up ticket (if only so we can
focus on proper testing separately). And in general, the more incremental we
can do stuff, the better.
> Address rows rather than partitions in SASI
> -------------------------------------------
>
> Key: CASSANDRA-11990
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11990
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Attachments: perf.pdf, size_comparison.png
>
>
> Currently, the lookup in SASI index would return the key position of the
> partition. After the partition lookup, the rows are iterated and the
> operators are applied in order to filter out ones that do not match.
> bq. TokenTree which accepts variable size keys (such would enable different
> partitioners, collections support, primary key indexing etc.),
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
