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

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/06/13 01:23:00 UTC

[jira] [Commented] (CASSANDRA-9596) Tombstone timestamps aren't used to skip SSTables while they are still in the memtable

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

Aleksey Yeschenko commented on CASSANDRA-9596:
----------------------------------------------

We do for {{collectTimeOrderedData()}} since CASSANDRA-7394 (2.0.9). I did miss {{collectAllData()}} there, though.

Benedict fixed it in CASSANDRA-9228 (2.1.6).

> Tombstone timestamps aren't used to skip SSTables while they are still in the memtable
> --------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9596
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9596
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Richard Low
>             Fix For: 2.0.x
>
>
> If you have one SSTable containing a partition level tombstone at timestamp t and all other SSTables have cells with timestamp < t, Cassandra will skip all the other SSTables and return nothing quickly. However, if the partition tombstone is still in the memtable it doesn’t skip any SSTables. It should use the same timestamp logic to skip all SSTables.



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