You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2014/06/12 21:43:04 UTC

[jira] [Commented] (CASSANDRA-7346) Modify reconcile logic to always pick a tombstone over a counter cell

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

Aleksey Yeschenko commented on CASSANDRA-7346:
----------------------------------------------

Also, as part of the ticket, fix the millisecond timestamps of the counter cells to use microseconds, for consistency with every other code path in Cassandra.

> Modify reconcile logic to always pick a tombstone over a counter cell
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-7346
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7346
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Richard Low
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             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)