[
https://issues.apache.org/jira/browse/CASSANDRA-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144208#comment-14144208
]
T Jake Luciani commented on CASSANDRA-7969:
-------------------------------------------
Running the tests I see the following failures:
{code}
[junit]
[junit] Testcase:
testTrackTimesRowTombstoneWithData(org.apache.cassandra.db.RangeTombstoneTest):
FAILED
[junit] expected:<999> but was:<2>
[junit] junit.framework.AssertionFailedError: expected:<999> but was:<2>
[junit] at
org.apache.cassandra.db.RangeTombstoneTest.assertTimes(RangeTombstoneTest.java:200)
[junit] at
org.apache.cassandra.db.RangeTombstoneTest.testTrackTimesRowTombstoneWithData(RangeTombstoneTest.java:150)
[junit]
[junit]
[junit] Testcase:
testTrackTimesRangeTombstone(org.apache.cassandra.db.RangeTombstoneTest): FAILED
[junit] expected:<1000> but was:<2>
[junit] junit.framework.AssertionFailedError: expected:<1000> but was:<2>
[junit] at
org.apache.cassandra.db.RangeTombstoneTest.assertTimes(RangeTombstoneTest.java:200)
[junit] at
org.apache.cassandra.db.RangeTombstoneTest.testTrackTimesRangeTombstone(RangeTombstoneTest.java:168)
[junit]
[junit]
[junit] Testcase:
testTrackTimesRangeTombstoneWithData(org.apache.cassandra.db.RangeTombstoneTest):
FAILED
[junit] expected:<999> but was:<0>
[junit] junit.framework.AssertionFailedError: expected:<999> but was:<0>
[junit] at
org.apache.cassandra.db.RangeTombstoneTest.assertTimes(RangeTombstoneTest.java:200)
[junit] at
org.apache.cassandra.db.RangeTombstoneTest.testTrackTimesRangeTombstoneWithData(RangeTombstoneTest.java:191)
[junit]
{code}
> 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)
