Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1793610667.1256751719514.JavaMail.jira@brutus>
Date: Wed, 28 Oct 2009 17:41:59 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Updated: (CASSANDRA-350) optimize away unnecessary range
 scans
In-Reply-To: <819290843.1249586714825.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis updated CASSANDRA-350:
-------------------------------------

    Attachment: 350-diff-to-v3.patch

> optimize away unnecessary range scans
> -------------------------------------
>
>                 Key: CASSANDRA-350
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-350
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Gary Dusbabek
>             Fix For: 0.5
>
>         Attachments: 350-diff-to-v3.patch, cassandra-350-v2-tests.patch, cassandra-350-v2.patch, cassandra-350-v3.patch, cassandra-350.patch
>
>
> Even when a the columns exist for a given key, they usually won't exist in all the sstable segments.  So avoiding the scan when the column index shows we can, will be a win.
> This is what the todo in SSTableSliceIterator is about:
>         // TODO push finishColumn down here too, so we can tell when we're done and optimize away the slice when the index + start/stop shows there's nothing to scan for

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.