You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Lightfoot (Jira)" <ji...@apache.org> on 2026/02/12 21:34:00 UTC

[jira] [Updated] (CASSANDRA-21170) Test failure: org.apache.cassandra.io.sstable.indexsummary.IndexSummaryTest#testLargeIndexSummary

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

Sam Lightfoot updated CASSANDRA-21170:
--------------------------------------
    Test and Documentation Plan:   (was: https://github.com/apache/cassandra/pull/4608

[https://pre-ci.cassandra.apache.org/job/cassandra/384/])

> Test failure: org.apache.cassandra.io.sstable.indexsummary.IndexSummaryTest#testLargeIndexSummary
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21170
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21170
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Local/Compaction
>            Reporter: Sam Lightfoot
>            Assignee: Sam Lightfoot
>            Priority: Normal
>             Fix For: 5.1
>
>
> [https://pre-ci.cassandra.apache.org/job/cassandra/347/testReport/junit/org.apache.cassandra.db.compaction.simple/CompactionDeleteRowRangeTest/Tests___test_jdk11_2_20___test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction__jdk11_x86_64/]
> [https://pre-ci.cassandra.apache.org/job/cassandra/351/testReport/junit/org.apache.cassandra.db.compaction.simple/CompactionDeleteRowRangeTest/Tests___test_jdk11_2_20___test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction__jdk11_x86_64/]
> The two deletes use the same CQL timestamp, so compaction should merge their overlapping range tombstones into a single open/close pair (no boundary markers). However, DeletionTime also includes local_delete_time (wall-clock seconds), which may differ between deletes if a second boundary is crossed during the flush. Differing local_delete_time causes the merger to treat them as distinct deletions, producing boundary markers instead. Using executeInternalWithNowInSec with a fixed nowInSec ensures both deletes get identical DeletionTime values.  
> Test introduced on 19/12/25 in [commit|https://github.com/apache/cassandra/commit/ff78780d6125010eb5909477c7a10a2540ca69bc#diff-94ab2916e6523ed70a01ba1b33870be9e96fc73f780e920b4fd776d7eb14cbee].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org