Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 1 Aug 2016 20:20:20 +0000 (UTC)
From: "DOAN DuyHai (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12977637.1465571216000.190572.1470082820533@Atlassian.JIRA>
In-Reply-To: <JIRA.12977637.1465571216000@Atlassian.JIRA>
References: <JIRA.12977637.1465571216000@Atlassian.JIRA> <JIRA.12977637.1465571216844@arcas>
Subject: [jira] [Commented] (CASSANDRA-11990) Address rows rather than
 partitions in SASI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 01 Aug 2016 20:20:22 -0000


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

DOAN DuyHai commented on CASSANDRA-11990:
-----------------------------------------

bq. backward-compatibility support

Can you clarify about this backward-compatibility ? Between what and what ?

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