[
https://issues.apache.org/jira/browse/CASSANDRA-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355659#comment-15355659
]
Alex Petrov commented on CASSANDRA-11990:
-----------------------------------------
Current status: I've extended the "right" part of {{TokenTree}} in order to
support row offset and implemented the rough prototype that would still read
{{DecoratedKey}} from index file (that might be beneficial if key cache is on,
so {{IndexInfo}} doesn't have to be re-fetched), and reads {{Clustering}} from
the data file, without {{localSatisfiedBy}} and additional post-filtering.
That may be further improved by reading the full row when it's needed just once
without reading clustering and then reading the row again, although I'll leave
it open for now, as this change should be rather localised.
> 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)
