Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 19 Sep 2013 19:47:51 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12669524.1379620066374.163954.1379620071974@arcas>
In-Reply-To: <JIRA.12669524.1379620066374@arcas>
References: <JIRA.12669524.1379620066374@arcas>
Subject: [jira] [Created] (CASSANDRA-6063) Rename internal classes and
 interfaces to represent the modern Cassandra terminology
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksey Yeschenko created CASSANDRA-6063:
--------------------------------------------

             Summary: Rename internal classes and interfaces to represent the modern Cassandra terminology
                 Key: CASSANDRA-6063
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6063
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Aleksey Yeschenko
            Priority: Minor
             Fix For: 3.0


Some of the class names we are using aren't exactly clear to the newcomers. We've already gone through the Table->Keyspace renaming, but it's not enough.

Other things to consider:

- ColumnFamilyStore -> Table
- Column -> Cell (where appropriate)
- ColumnFamily -> CellFormation (CellGroup, something different?)
- Row -> Partition (where appropriate)
- RowMutation -> PartitionMutation


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