[
https://issues.apache.org/jira/browse/CASSANDRA-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549846#comment-13549846
]
André Cruz commented on CASSANDRA-3237:
---------------------------------------
As an example, supposing I have an older schema with SuperColumns like this:
{code:xml}
ROWKEY:
SC1:
C1: val
C2: val
SC2:
C3: val
C4: val
{code}
With this schema I can query cassandra for "the first object in row ROWKEY",
which would return:
{code:xml}
SC1: (C1: val, C2: val)
{code}
It seems that converting this to CompositeType columns the schema would look
like:
{code:xml}
ROWKEY:
SC1:C1: val
SC1:C2: val
SC2:C3: val
SC2:C4: val
{code}
So using this converted schema, if I wanted to obtain the first object of that
row, it seems that I would obtain:
{code:xml}
SC1:C1: val
{code}
How is this converted so that compatibility is preserved?
Thanks.
> 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
