[jira] [Comment Edited] (CASSANDRA-11990) Address rows rather than partitions in SASI

["Alex Petrov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393773#comment-15393773 ] 

Alex Petrov edited comment on CASSANDRA-11990 at 7/26/16 1:20 PM:
------------------------------------------------------------------

Attached is the size comparison graph between trunk and this branch. 

Smaller is better. As with the performance test, I'm inserting 100 partitions, containing 10, 100 and 1000 clusterings, with different-sized partition keys.

cc [~xedin]


was (Author: ifesdjeen):
Attached is the size comparison graph between trunk and this branch. 

Smaller is better. As with the performance test, I'm inserting 100 partitions, containing 10, 100 and 1000 clusterings, with different-sized partition keys.

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