cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Low (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-7346) Row deletes use incompatible timestamps on counter column families
Date Tue, 03 Jun 2014 13:54:01 GMT
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)

Mime
View raw message