Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 2 Jul 2015 16:18:04 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12832471.1432541421000.86291.1435853884743@Atlassian.JIRA>
In-Reply-To: <JIRA.12832471.1432541421000@Atlassian.JIRA>
References: <JIRA.12832471.1432541421000@Atlassian.JIRA>
 <JIRA.12832471.1432541421751@arcas>
Subject: [jira] [Commented] (CASSANDRA-9471) Columns should be backed by a
 BTree, not an array
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benedict commented on CASSANDRA-9471:
-------------------------------------

[~blambov]: just letting you know that I'm rebasing this, which may take a little while. The btree-only changes (i.e. the majority of the work) are still good for review though.

> Columns should be backed by a BTree, not an array
> -------------------------------------------------
>
>                 Key: CASSANDRA-9471
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9471
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>             Fix For: 3.0 beta 1
>
>
> Follow up to 8099. 
> We have pretty terrible lookup performance as the number of columns grows (linear). In at least one location, this results in quadratic performance. 
> We don't however want this structure to be either any more expensive to build, nor to store. Some small modifications to BTree will permit it to serve here, by permitting efficient lookup by index, and calculation _of_ index for a given key.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)