Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 11 Mar 2015 16:12:38 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12781162.1426076610000.64846.1426090358551@Atlassian.JIRA>
In-Reply-To: <JIRA.12781162.1426076610000@Atlassian.JIRA>
References: <JIRA.12781162.1426076610000@Atlassian.JIRA>
 <JIRA.12781162.1426076610784@arcas>
Subject: [jira] [Updated] (CASSANDRA-8946) Make SSTableScanner always
 respect its bound
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict updated CASSANDRA-8946:
--------------------------------
    Fix Version/s: 2.1.4

> Make SSTableScanner always respect its bound
> --------------------------------------------
>
>                 Key: CASSANDRA-8946
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8946
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Benedict
>             Fix For: 2.1.4
>
>
> When {{SSTableScanner}} takes a {{DataRange}}, it doesn't fully respect the bounds provided as it always generate a {{Bounds}} object, thus potentially ending up including a key it should have excluded. It's currently compensated by in {{ColumnFamilyStore.getSequentialIterator}} but that is still an unexpected behavior and is such error prone. We should fix that and remove the compensation in {{ColumnFamilyStore.getSequentialIterator}}.


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