cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2440) Merge ColumnOrSuperColumn and Counter thrift structure to avoid most of the counter API call duplication
Date Sat, 09 Apr 2011 20:36:05 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017950#comment-13017950
] 

Stu Hood commented on CASSANDRA-2440:
-------------------------------------

Looks good. Could we perhaps also merge CounterSuperColumn with SuperColumn by giving SuperColumn
two lists? There really isn't any such thing as a CounterSuperColumn per-say... just a SuperColumn
holding counters.

> Merge ColumnOrSuperColumn and Counter thrift structure to avoid most of the counter API
call duplication
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2440
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2440
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 0.8
>
>         Attachments: cassandra.thrift
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> Having duplicate calls for all counter operation is ugly. Distinguishing a Column from
a CounterColumn is a good idea, but I feel we went too far in making counters an API on its
own. This ticket proposes to merge the Counter and ColumnOrSuperColumn thrift structure (while
keeping CounterColumn and CounterSuperColumn) and to remove all the duplicate API calls.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message