cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11990) Address rows rather than partitions in SASI
Date Wed, 29 Jun 2016 19:01:08 GMT


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:
>             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

View raw message