[
https://issues.apache.org/jira/browse/CASSANDRA-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko reopened CASSANDRA-7346:
------------------------------------------
Assignee: Aleksey Yeschenko
All right. Pushed to https://github.com/iamaleksey/cassandra/commits/7346 (the
last and only commit there).
Initially was going to convert the timestamps in CounterMutation itself,
however, it turned out to be easier to modify CQL3/CQL2/Thrift (it's all
isolated to UpdateParameters for CQL3 and two methods in CassandraServer for
Thrift).
Updated CQL2 too, even though it's gone from 3.0.
> Row deletes use incompatible timestamps on counter column families
> ------------------------------------------------------------------
>
> Key: CASSANDRA-7346
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7346
> Project: Cassandra
> Issue Type: Bug
> Reporter: Richard Low
> Assignee: Aleksey Yeschenko
> Fix For: 2.1.0
>
>
> For counters, timestamps are automatically computed to be milliseconds since
> the epoch. For everything else, when not specified manually, they are
> microseconds since the epoch. This means if you delete a counter row,
> subsequent updates are lost unexpectedly.
> I know that deleting counters is not recommended, but that's only because
> deletes and incs don't commute. If you know you have stopped incs, then
> delete, then start again (with some external synchronization) then deleting
> is fine.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
