You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Joshua McKenzie (JIRA)" <ji...@apache.org> on 2016/11/02 15:41:59 UTC

[jira] [Updated] (CASSANDRA-12792) delete with timestamp long.MAX_VALUE for the whole key creates tombstone that cannot be removed.

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

Joshua McKenzie updated CASSANDRA-12792:
----------------------------------------
       Reviewer: Branimir Lambov
    Description: 
In db/compaction/LazilyCompactedRow.java 
we only check for  <  MaxPurgeableTimeStamp  

eg:

(this.maxRowTombstone.markedForDeleteAt < getMaxPurgeableTimestamp())

this should probably be <= 



  was:

In db/compaction/LazilyCompactedRow.java 
we only check for  <  MaxPurgeableTimeStamp  

eg:

(this.maxRowTombstone.markedForDeleteAt < getMaxPurgeableTimestamp())

this should probably be <= 




> delete with timestamp long.MAX_VALUE for the whole key creates tombstone that cannot be removed. 
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12792
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12792
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>            Reporter: Ian Ilsley
>            Assignee: Joel Knighton
>
> In db/compaction/LazilyCompactedRow.java 
> we only check for  <  MaxPurgeableTimeStamp  
> eg:
> (this.maxRowTombstone.markedForDeleteAt < getMaxPurgeableTimestamp())
> this should probably be <= 



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