cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jocelyn Racoillet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-998) Replace SuperColumn and ColumnFamily structures
Date Mon, 25 Apr 2011 12:15:06 GMT

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

Jocelyn Racoillet commented on CASSANDRA-998:
---------------------------------------------

Note to people looking for an alternative to SuperColumns, this looks promising: composite
columns and CompositeType comparer (CASSANDRA-2231).

> Replace SuperColumn and ColumnFamily structures
> -----------------------------------------------
>
>                 Key: CASSANDRA-998
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-998
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>             Fix For: 0.8 beta 1
>
>
> The most important concepts to come out of CASSANDRA-674 were the Slice, Metadata and
ColumnKey structures.
> As a replacement for SuperColumns and ColumnFamilies in the current codebase, Slices
can addtionally:
> * Represent arbitrarily nested columns
> * Allow for eventually consistent range deletes (equivalent to a CF containing multiple
'markedForDelete' values)
> * Be used for memory efficient compactions, since they encapsulate nesting and can be
iterated
> * Eliminate code duplication for SuperColumn handling
> This is an umbrella ticket for the task of replacing the SuperColumn and ColumnFamily
datastructures in the codebase, preferably with something like Slice.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message