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-7394) Fix CollationController#collectTimeOrderedData() mostRecentRowTombstone tracking
Date Wed, 25 Jun 2014 21:19:24 GMT

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

Jonathan Ellis commented on CASSANDRA-7394:
-------------------------------------------

Ship it!

> Fix CollationController#collectTimeOrderedData() mostRecentRowTombstone tracking
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7394
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7394
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 2.0.9, 2.1.0
>
>         Attachments: 7394.txt
>
>
> As of now, collectTimeOrderedData() will try to read from at least one sstable, even
if the memtable has a row tombstone with a higher timestamp than any max timestamp in the
sstable. If we initiate mostRecentRowTombstone with the value from the memtables and not Long.MIN_VALUE,
reading from the sstables can be avoided entirely in this scenario.
> Current tracking is also broken b/c we update mostRecentRowTombstone value with the one
read from the last sstable, unconditionally, even if it's a lesser tombstone than we used
to have tracked.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message