cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Cruz (JIRA) <>
Subject [jira] [Commented] (CASSANDRA-3237) refactor super column implmentation to use composite column names instead
Date Fri, 11 Jan 2013 13:32:15 GMT


André Cruz commented on CASSANDRA-3237:

Ah, great. But sorry to insist, it's just that I'm trying to convert my schemas away from
SCF, and so I'm doing manually what this patch does automatically. I would like to know how
can I query this CompositeType model to obtain those SCF compatible results. Can it be done
with just one query?

Say, if I wanted the first 2 SuperColumns, so I was expecting all SC1 and SC2 data, can I
query Cassandra for the first 2 distinct values of the first component of a CompositeType

Thanks again.
> 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