cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Boudreault (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8744) Ensure SSTableReader.first/last are honoured universally
Date Fri, 06 Feb 2015 16:22:36 GMT

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

Alan Boudreault commented on CASSANDRA-8744:
--------------------------------------------

[~benedict] It doesn't look like an issue I can easily reproduce with a specific use case
. Am I correct, or I sould be able to reproduce that in some way?

> 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)

Mime
View raw message