Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 7 May 2013 13:23:21 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12504834.1303344750704.280086.1367933001038@arcas>
In-Reply-To: <JIRA.12504834.1303344750704@arcas>
References: <JIRA.12504834.1303344750704@arcas>
Subject: [jira] [Commented] (CASSANDRA-2524) Use SSTableBoundedScanner for
 cleanup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-2524:
-------------------------------------------

I think the analog would be to create a SSTS with a Range.
                
> Use SSTableBoundedScanner for cleanup
> -------------------------------------
>
>                 Key: CASSANDRA-2524
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2524
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>            Assignee: Marcus Eriksson
>            Priority: Minor
>              Labels: lhf
>             Fix For: 2.0
>
>         Attachments: 0001-CASSANDRA-2524-use-SSTableBoundedScanner-for-cleanup.patch, 0001-Use-a-SSTableBoundedScanner-for-cleanup-and-improve-cl.txt, 0002-Oops.-When-indexes-or-counters-are-in-use-must-continu.txt
>
>
> SSTableBoundedScanner seeks rather than scanning through rows, so it would be significantly more efficient than the existing per-key filtering that cleanup does.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira