[
https://issues.apache.org/jira/browse/CASSANDRA-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360655#comment-15360655
]
DOAN DuyHai commented on CASSANDRA-11990:
-----------------------------------------
[~ifesdjeen] There is also a big change in {{SSTableReader}} that is required
to implement this JIRA. Currently this class only exposes the method
{{DecoratedKey SSTableReader.keyAt(long indexPosition)}}. We'll need to
introduce a new method {{Unfiltered SSTableReader.rowAt(long rowOffset)}}.
Modifying the {{SSTableReader}} has a big impact on the overall storage engine
> 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)