[
https://issues.apache.org/jira/browse/CASSANDRA-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613122#comment-14613122
]
Sylvain Lebresne commented on CASSANDRA-9471:
---------------------------------------------
Side note: if the changes to {{Columns}} are not hard to rebase, I'd personally
be fine with just rebasing that ticket as is (without bothering splitting it in
2 tickets) for the sake of saving you some time. At least for CASSANDRA-9705, I
don't plan on having much of {{Columns}} going obsolete (the indexability will
be most likely much less used but will still be handy, and we'll still rely
heavily-ish on {{contains}} which is currently not terribly efficient). And of
course, that still doesn't precludes from consider other implementation of
{{Columns}} later.
Anyway, fine with whatever way you prefer, but just to say that if splitting
into 2 tickets takes you the same time than just rebasing the whole patch, I'd
personally just go with the second option.
> 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)
