Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 15 Jan 2016 16:53:39 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12837521.1434146054000.123328.1452876819915@Atlassian.JIRA>
In-Reply-To: <JIRA.12837521.1434146054000@Atlassian.JIRA>
References: <JIRA.12837521.1434146054000@Atlassian.JIRA>
 <JIRA.12837521.1434146054344@arcas>
Subject: [jira] [Resolved] (CASSANDRA-9596) Tombstone timestamps aren't used
 to skip SSTables while they are still in the memtable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-9596?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne resolved CASSANDRA-9596.
-----------------------------------------
    Resolution: Duplicate

> 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
>            Reporter: Richard Low
>             Fix For: 2.1.x
>
>
> If you have one SSTable containing a partition level tombstone at timesta=
mp t and all other SSTables have cells with timestamp < t, Cassandra will s=
kip all the other SSTables and return nothing quickly. However, if the part=
ition tombstone is still in the memtable it doesn=E2=80=99t skip any SSTabl=
es. It should use the same timestamp logic to skip all SSTables.


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