You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Richard Low (JIRA)" <ji...@apache.org> on 2014/06/03 15:54:01 UTC
[jira] [Created] (CASSANDRA-7346) Row deletes use incompatible
timestamps on counter column families
Richard Low created CASSANDRA-7346:
--------------------------------------
Summary: 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
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)