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

Sam Lightfoot reassigned CASSANDRA-21163:
-----------------------------------------

    Assignee: Sam Lightfoot  (was: Arvind Kandpal)

> Test failure: 
> org.apache.cassandra.db.compaction.simple.CompactionDeleteRowRangeTest#test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21163
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21163
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Local/SSTable
>            Reporter: Sam Lightfoot
>            Assignee: Sam Lightfoot
>            Priority: Normal
>             Fix For: 5.x
>
>
> [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.  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to