[
https://issues.apache.org/jira/browse/CASSANDRA-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402577#comment-15402577
]
Alex Petrov commented on CASSANDRA-11990:
-----------------------------------------
We've tried out the idea of using the column offset for the query optimisation.
I've showed results to [~xedin] and [~beobal] and for now we concluded that we
can leave this optimisation out for now (as it'd be a significant change). It
might come very handy if / when we have an ability to compare clusterings (by
some sort of order-preserving hash function) rather than just offsets.
Only big thing that's left is to bring back the backward-compatibility support,
which I was leaving for the end as code got restructured several times. I'll
get to it and hope to present a preliminary result shortly.
> 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)
