[
https://issues.apache.org/jira/browse/CASSANDRA-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181990#comment-13181990
]
Mck SembWever commented on CASSANDRA-3237:
------------------------------------------
We using supercolumns to provide us "buckets of counters". (I've attached the
irc log discussing our valid use case for supercolumns).
Today with supercolumns you can select multiple supercolumns in one query.
With composite columns you have to do a slice for each bucket. In our use case
this explodes one query into hundreds of queries.
Will the existing supercoumn API exist so we can continue doing single queries,
or will it become possible to do "get_multislice" (get one row with mutliple
column slices)?
> 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
