[
https://issues.apache.org/jira/browse/CASSANDRA-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079306#comment-14079306
]
Aleksey Yeschenko commented on CASSANDRA-7647:
----------------------------------------------
+1 (although there is no difference between RangeTombstone#minTimestamp() and
RangeTombstone#maxTimestamp(), and in 2.1 they are both gone in favor of
RangeTombstone#timestamp()).
> Track min/max timestamps of range tombstones
> --------------------------------------------
>
> Key: CASSANDRA-7647
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7647
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> 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)
