[jira] [Commented] (CASSANDRA-6999) Batchlog replay should account for CF truncation records

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

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

Aleksey Yeschenko commented on CASSANDRA-6999:
----------------------------------------------

So, there are two sides to this.

One is truncations from the past, relative to the replay session. To handle these properly we should filter-out modifications that happened before a truncation record.

The other is future truncations + hints to unavailable nodes. These hints should be written with written_at timestamp (millis), since that's what HHOM uses to decide whether or not to apply the hint.

Pushed the fix to https://github.com/iamaleksey/cassandra/commits/6999

> Batchlog replay should account for CF truncation records
> --------------------------------------------------------
>
>                 Key: CASSANDRA-6999
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6999
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2.17, 2.0.7, 2.1 beta2
>
>
> Just as HHOM does, BM should properly handle column families' truncation records and not replay mutations that are younger that the last known record.



--
This message was sent by Atlassian JIRA
(v6.2#6252)