cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3237) refactor super column implmentation to use composite column names instead
Date Mon, 03 Sep 2012 10:57:07 GMT


Sylvain Lebresne commented on CASSANDRA-3237:

I'm not really sure we need to really have 2 phases, and in any case I'm not convinced a startup
scrub is the right approach.

I think that what we need is to write conversions functions for <CF with SC> to and
from <CF with equivalent composite> and for requests on both kind of CF. With those,
I think you can directly remove the use of SC internally, you just use those functions for
1) compatibility when sending/receiving to/from older nodes and 2) decode old SC format when
reading old sstables. Of course that's much more easily said than done.
> refactor super column implmentation to use composite column names instead
> -------------------------------------------------------------------------
>                 Key: CASSANDRA-3237
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Matthew F. Dennis
>            Assignee: Vijay
>            Priority: Minor
>              Labels: ponies
>             Fix For: 1.3
>         Attachments: cassandra-supercolumn-irc.log
> super columns are annoying.  composite columns offer a better API and performance.  people
should use composites over super columns.  some people are already using super columns.  C*
should implement the super column API in terms of composites to reduce code, complexity and
testing as well as increase performance.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message