[
https://issues.apache.org/jira/browse/CASSANDRA-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-2440:
----------------------------------------
Attachment: cassandra.thrift
Attaching a tentative API for now. After the merge of Counter and
ColumnOrSuperColumn, the only method specific to counters are
* add - because we still distinguish Column and CounterColumn, so we can't
use insert here.
* remove_counter - We don't have timestamps for counters (more precisely we
use server timestamps) and we can't have the timestamp optional in the remove
method.
For the remove_counter method, I could be fine keeping only the remove method
and ignoring the timestamp if it's a counter CF, but I'm not sure it is really
cleaner and since counter removal is a bit limited it feels like a good idea to
keep a separate call.
> 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
