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-8914) Don't lookup maxPurgeableTimestamp unless we need to
Date Thu, 05 Mar 2015 10:03:38 GMT
Marcus Eriksson created CASSANDRA-8914:
------------------------------------------

             Summary: Don't lookup maxPurgeableTimestamp unless we need to
                 Key: CASSANDRA-8914
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8914
             Project: Cassandra
          Issue Type: Bug
            Reporter: Marcus Eriksson
            Assignee: Marcus Eriksson
             Fix For: 2.1.4


Currently we look up the maxPurgeableTimestamp in LazilyCompactedRow constructor, we should
only do that if we have to (ie, if we know there is a tombstone to possibly drop)



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

Mime
View raw message