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, 14 Jan 2013 11:40:15 GMT


Sylvain Lebresne commented on CASSANDRA-3237:

bq. and so I'm doing manually what this patch does automatically

I'm afraid you cannot do *exactly* what the patch does, not at the moment at least, because
said patch uses a way to count results that CQL3 uses and that is not exposed to thrift (see

bq. it's just that I'm trying to convert my schemas away from SCF

I know there is a lot of "don't use super columns" floating out there, but honestly on the
thrift side, the super column API is probably going to be more convenient if your use case
do map well to them. And while SC do have limitations like 'they are always deserialized in
their entirety', this patch fixes a good part of them moving forward. Just saying.
> refactor super column implmentation to use composite column names instead
> -------------------------------------------------------------------------
>                 Key: CASSANDRA-3237
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Matthew F. Dennis
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: ponies
>             Fix For: 2.0
>         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