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

Aleksey Yeschenko updated CASSANDRA-6063:
-----------------------------------------

    Description: 
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)- done in 
e50d6af12fabac98e3cb4bd589e2b92212b041f4
- ColumnFamily -> CellFormation (CellGroup, something different?)
- Row -> Partition (where appropriate)
- RowMutation -> PartitionMutation


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



> 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: 2.1
>
>
> 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)- done in 
> e50d6af12fabac98e3cb4bd589e2b92212b041f4
> - ColumnFamily -> CellFormation (CellGroup, something different?)
> - Row -> Partition (where appropriate)
> - RowMutation -> PartitionMutation



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to