You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2014/07/30 14:16:38 UTC

[jira] [Updated] (CASSANDRA-7647) Track min/max timestamps of range tombstones

     [ https://issues.apache.org/jira/browse/CASSANDRA-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-7647:
---------------------------------------

    Attachment:     (was: 0001-track-rt-in-min-max-timestamps.patch)

> Track min/max timestamps of range tombstones
> --------------------------------------------
>
>                 Key: CASSANDRA-7647
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7647
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 2.0.10, 2.1.0
>
>         Attachments: 0001-track-rt-in-min-max-timestamps.patch
>
>
> When compacting etc. we don't track min/max timestamps of range tombstones, meaning a compacted sstable with only RTs will get bad values.
> End result can be that we drop the sstable since it might look like it only contains tombstones and is older than all other sstables, and we lose the valid RT.



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