[
https://issues.apache.org/jira/browse/HBASE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609613#action_12609613
]
Bryan Duxbury commented on HBASE-696:
-------------------------------------
I'm not sure that there would be much benefit to putting the timestamp in the
filter. It'd only be useful in the case where you're always looking for EXACT
matches on row/col/ts, since you can't do any "less-than" behavior there.
Likewise, I think the column is of dubious value. It's only really handy if you
have a lot of columns and the one you are looking for is somewhere in the
middle of the range, which would require a lot of seeking.
I think that we should go with a fewer-options approach and just make the
row-only bloom filter. If someone can make the case for more things going in
the filter down the road, then we'll tackle it at that point.
> 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
> Assignee: Jim Kellerman
> 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.
