cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-6063) Rename internal classes and interfaces to represent the modern Cassandra terminology
Date Sat, 21 Dec 2013 12:22:10 GMT

     [ 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? ColumnFamily?
- -Column -> Cell (where appropriate)- done in e50d6af12fabac98e3cb4bd589e2b92212b041f4
- ColumnFamily -> CellFormation (CellGroup, something different?)
- Row -> Partition (where appropriate)
- RowMutation -> Mutation


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



Actually, I would prefer to go with ColumnFamily for ColumnFamilyStore, and not Table. But
renaming both current ColumnFamily to CellGroup and ColumnFamilyStore to ColumnFamily would
be evil, so I'd postpone this rename (CFS -> CF) to 3.0, if at all. It's not a confusing
class name.

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



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

Mime
View raw message