[
https://issues.apache.org/jira/browse/HBASE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609421#action_12609421
]
Jim Kellerman commented on HBASE-696:
-------------------------------------
> Bryan Duxbury - 30/Jun/08 02:56 PM
> I thought it might be useful to point out that the bloom filter wouldn't
> really be used for
> scanning, either, since you're already going to have locality proceeding
> through the file
> as you scan. There wouldn't be much point in checking if a storefile has the
> next row or
> not.
You are quite right. bloomfilters have little to do with scanners. Their
primary use is for get
> Make bloomfilter true/false and self-sizing
> -------------------------------------------
>
> Key: HBASE-696
> URL: https://issues.apache.org/jira/browse/HBASE-696
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Fix For: 0.2.0
>
>
> Remove bloomfilter options. Only one bloomfilter type makes sense in hbase
> context. Also, make bloomfilter self-sizing; you know size when flushing.
> Putting in 0.2 for now because its API change (for the simpler). We can punt
> later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
