You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/01/26 19:35:35 UTC

[jira] [Resolved] (CASSANDRA-6063) Rename internal classes and interfaces to represent the modern Cassandra terminology

     [ https://issues.apache.org/jira/browse/CASSANDRA-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko resolved CASSANDRA-6063.
------------------------------------------
    Resolution: Duplicate

> 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 -> ColumnFamily (non-critical)
> - -Column -> Cell (where appropriate)- done in e50d6af12fabac98e3cb4bd589e2b92212b041f4
> - ColumnFamily -> Cells
> - Row -> Partition (PartitionFragment?) (where appropriate)
> - -RowMutation -> Mutation- done in 6bbb13b9b0fe62de2a2140055af2ea6968c73ccc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)