cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9471) Columns should be backed by a BTree, not an array
Date Fri, 03 Jul 2015 09:45:04 GMT


Sylvain Lebresne commented on CASSANDRA-9471:

bq.  If we choose not to include this feature, it would be better to implement these directly

How much better? Thinking out loud here, but we're a database, we're dealing with sorted stuff
all the time. So even outside of its use (or not) by {{Columns}}, having a more capable {{BtreeSet}}
implementation, one that can act more like an efficient sorted list, feels to me like something
that would be useful to have in our tool belt. Meaning by that it sounds from you comments
that the  indexability does add much complexity to the implementation(disclaimer: I haven't
looked at the patch) , so if its cost is really small, maybe it's worth getting the flexibility?

> Columns should be backed by a BTree, not an array
> -------------------------------------------------
>                 Key: CASSANDRA-9471
>                 URL:
>             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

View raw message