Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 9 Feb 2015 19:21:35 +0000 (UTC)
From: "Yuki Morishita (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12772693.1423143021000.302851.1423509695536@Atlassian.JIRA>
In-Reply-To: <JIRA.12772693.1423143021000@Atlassian.JIRA>
References: <JIRA.12772693.1423143021000@Atlassian.JIRA>
 <JIRA.12772693.1423143021848@arcas>
Subject: [jira] [Commented] (CASSANDRA-8744) Ensure SSTableReader.first/last
 are honoured universally
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yuki Morishita commented on CASSANDRA-8744:
-------------------------------------------

Patch (63d3c54ade5c15fafb0ac129e0bf101fb88afc1a) LGTM. +1.

> Ensure SSTableReader.first/last are honoured universally
> --------------------------------------------------------
>
>                 Key: CASSANDRA-8744
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8744
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Critical
>             Fix For: 2.1.4
>
>
> Split out from CASSANDRA-8683; we don't honour the first/last properties of an sstablereader, and we tend to assume that we do. This can cause problems in LCS validation compactions, for instance, where a scanner is assumed to only cover the defined range, but may return data either side of that range. In general it is only wasteful to not honour these ranges anyway.


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