Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 29 Mar 2013 16:23:15 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12639839.1364574137480.77099.1364574195729@arcas>
In-Reply-To: <JIRA.12639839.1364574137480@arcas>
References: <JIRA.12639839.1364574137480@arcas>
Subject: [jira] [Created] (CASSANDRA-5403) Clean up ColumnFamily,
 ISortedColumns heirarchy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jonathan Ellis created CASSANDRA-5403:
-----------------------------------------

             Summary: Clean up ColumnFamily, ISortedColumns heirarchy
                 Key: CASSANDRA-5403
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5403
             Project: Cassandra
          Issue Type: Bug
            Reporter: Jonathan Ellis
            Assignee: Jonathan Ellis


CF wraps ISC but adds no real functionality of its own (post-supercolumn cleanup).

This means that we're wasting allocations every time we create a CF/ISC pair when really one would do.

Other things that would be nice to clean up:
# We often create an empty CF as a placeholder that should not be modified, and rely on convention to avoid such modification.  We could enforce this with a new CF/ISC subclass.
# Many places still use TMBSC where ABSC would be adequate and cheaper
# Other places still (ModificationStatement; others?) would be fine using a column container with no sorting requirement at all

--
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