cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-325) Column bloomfilter not exploited
Date Thu, 30 Jul 2009 16:39:14 GMT

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

Jun Rao commented on CASSANDRA-325:
-----------------------------------

I won't mind getting rid of the column-level BF for now. Just a few more comments.

Yes, we are deserializing the whole column index (for every read). However, the column index
is not dense and doesn't tell you exactly whether a column or a list of columns exist. So,
by using a BF, one could save an extra I/O if the column is not present.



> 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
>
> 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.


Mime
View raw message