cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mck SembWever (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3237) refactor super column implmentation to use composite column names instead
Date Wed, 07 Nov 2012 20:46:12 GMT

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

Mck SembWever commented on CASSANDRA-3237:
------------------------------------------

{quote}... 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...{quote}
Despite there being no startup scrub this still means that a manual `nodetool upgradesstables`
will using these conversions functions to rewrite all sstables to composite columns?
                
> 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.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: http://www.atlassian.com/software/jira

Mime
View raw message