cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3237) refactor super column implmentation to use composite column names instead
Date Fri, 11 Jan 2013 12:40:16 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551083#comment-13551083
] 

Sylvain Lebresne commented on CASSANDRA-3237:
---------------------------------------------

bq. How is this converted so that compatibility is preserved?

Exactly the way you've described it. But the code also convert queries on super columns, so
that the query that select the first super column of a row still return all the super column,
not just the first subcolumn.
                
> refactor super column implmentation to use composite column names instead
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3237
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3237
>             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: http://www.atlassian.com/software/jira

Mime
View raw message