[ https://issues.apache.org/jira/browse/CASSANDRA-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538477#comment-14538477 ]
Ariel Weisberg commented on CASSANDRA-8914: ------------------------------------------- Was this a correctness fixed or a performance improvement? Can't tell from the description. > 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.5 > > Attachments: > 0001-only-get-maxPurgableTimestamp-if-we-know-there-are-t.patch, 8914-v2.patch > > > 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)