Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B54C109AA for ; Thu, 30 Jan 2014 14:50:16 +0000 (UTC) Received: (qmail 73991 invoked by uid 500); 30 Jan 2014 14:50:15 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 73827 invoked by uid 500); 30 Jan 2014 14:50:12 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 73782 invoked by uid 99); 30 Jan 2014 14:50:10 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jan 2014 14:50:10 +0000 Date: Thu, 30 Jan 2014 14:50:10 +0000 (UTC) From: "Ignace Desimpel (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6638) SSTableScanner can Skip Rows with vnodes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886624#comment-13886624 ] Ignace Desimpel commented on CASSANDRA-6638: -------------------------------------------- Sorry, my mistake. > SSTableScanner can Skip Rows with vnodes > ---------------------------------------- > > Key: CASSANDRA-6638 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6638 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Tyler Hobbs > Assignee: Sylvain Lebresne > Priority: Blocker > Fix For: 2.0.5 > > Attachments: 6638-repro-test.txt, 6638.txt > > > CASSANDRA-2524 added multiple range support to SSTableScanner, but it looks like there is at least one case where keys can be skipped. This can result in cleanup removing legitimate keys. > See the attached patch that adds a unit test to reproduce the case. -- This message was sent by Atlassian JIRA (v6.1.5#6160)