Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1950746394.1249696394786.JavaMail.jira@brutus>
Date: Fri, 7 Aug 2009 18:53:14 -0700 (PDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-325) Column bloomfilter not exploited
In-Reply-To: <264370685.1248911354834.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-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740817#action_12740817 ] 

Jonathan Ellis commented on CASSANDRA-325:
------------------------------------------

It doesn't make sense to me to make this an option.  For name-based slices it's always going to be an overall win.  For range-based slices, it's mostly a no-op since the SliceIterator just skips a few bytes and doesn't actually deserialize it.  Since we are doing buffered reads that's almost free.  It's not worth letting someone generate complete garbage answers by changing that config value on a CF that already has data on disk.

> Column bloomfilter not exploited
> --------------------------------
>
>                 Key: CASSANDRA-325
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-325
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jun Rao
>            Assignee: Jonathan Ellis
>             Fix For: 0.4
>
>         Attachments: 325-v2.patch, 325.patch
>
>
> There is a bloomfilter created for all columns per row in SSTables. The bloomfilter is deserialized during read, but is not checked.

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