[
https://issues.apache.org/jira/browse/CASSANDRA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915078#action_12915078
]
Stu Hood commented on CASSANDRA-998:
------------------------------------
I'm working on rebasing 1092. Coming back to this issue after a few months,
it's clear that the approach I was taking with 1095 and 1106 was much too
aggressive, so I've marked them invalid. Applying identical structures to the
memtable and sstables may end up being the right idea in the long run, but
there is no way it will be committed in the short term.
> 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.
-
You can reply to this email to add a comment to the issue online.
