[jira] [Commented] (CASSANDRA-3237) refactor super column implmentation to use composite column names instead

["Robbie Strickland (JIRA)" <ji...@apache.org>]

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

Robbie Strickland commented on CASSANDRA-3237:
----------------------------------------------

Will there be a migration path for the underlying SC data?  I have two years worth of data in SCs for the same reason as Mck. Having experienced the pain of the 0.6.x -> 0.7.x migration, I'm not thrilled about the idea of figuring out how to get all my data into a new format.  No matter how much the C* community may despise SCs, a lot of people have a lot of data stored in them for valid reasons, so there needs to be a well-defined migration path.
                
> 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
>            Priority: Minor
>              Labels: ponies
>             Fix For: 1.2
>
>         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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira