cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-7969) Properly track min/max timestamps and maxLocalDeletionTimes for range and row tombstones
Date Thu, 18 Sep 2014 07:42:33 GMT
Marcus Eriksson created CASSANDRA-7969:
------------------------------------------

             Summary: Properly track min/max timestamps and maxLocalDeletionTimes for range
and row tombstones
                 Key: CASSANDRA-7969
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7969
             Project: Cassandra
          Issue Type: Bug
            Reporter: Marcus Eriksson
            Assignee: Marcus Eriksson
             Fix For: 2.0.11
         Attachments: 0001-track-min-max-timestamps-and-maxLocalDeletionTime-co.patch

First problem is that when we have only row or range tombstones in an sstable we dont update
the maxLocalDeletionTime for the sstable

Second problem is that if we have a range tombstone in an sstable, minTimestamp will always
be Long.MIN_VALUE for flushed sstables due to how we set the default values for the variables



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message