[
https://issues.apache.org/jira/browse/CASSANDRA-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360658#comment-15360658
]
Alex Petrov commented on CASSANDRA-11990:
-----------------------------------------
[~doanduyhai] I know this has a big impact on the storage engine. However,
implementing {{Unfiltered SSTableReader.rowAt(long rowOffset)}} is
non-trivial, as it'll also involve extending the token for clustering order.
I've opted out for a simpler approach for now, which is only reading out the
clustering keys and using them for sorting for sakes of proof-of-concept. This
change was very small and non-intrusive and leaves us enough room to improve it
in future.
> 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
>
> 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)
