You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2011/02/09 08:59:57 UTC
[jira] Resolved: (CASSANDRA-998) Replace SuperColumn and
ColumnFamily structures
[ https://issues.apache.org/jira/browse/CASSANDRA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood resolved CASSANDRA-998.
--------------------------------
Resolution: Invalid
Waay too invasive.
> 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
>
>
> 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