cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8914) Don't lookup maxPurgeableTimestamp unless we need to
Date Mon, 11 May 2015 19:59:01 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538550#comment-14538550
] 

Jonathan Ellis commented on CASSANDRA-8914:
-------------------------------------------

Performance.

> Don't lookup maxPurgeableTimestamp unless we need to
> ----------------------------------------------------
>
>                 Key: CASSANDRA-8914
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8914
>             Project: Cassandra
>          Issue Type: Improvement
>            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)

Mime
View raw message