You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2008/01/18 08:31:34 UTC

[jira] Updated: (HADOOP-2654) CountingBloomFilter can overflow its storage

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

Stu Hood updated HADOOP-2654:
-----------------------------

    Attachment: counting-overflow.patch

Here is a patch that compares the value of each bucket to Byte.MAX_VALUE to ensure that buckets stay in range.

> CountingBloomFilter can overflow its storage
> --------------------------------------------
>
>                 Key: HADOOP-2654
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2654
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: Stu Hood
>         Attachments: counting-overflow.patch
>
>
> The org.onelab.filter.CountingBloomFilter implementation does not check the value of a bucket before incrementing/decrementing it. The buckets in a Counting Bloom filter must not be allowed to overflow, and if they reach their maximum value, they must not be allowed to decrement. This is the only way to preserve the assumptions of the filter (without larger buckets). See: http://en.wikipedia.org/wiki/Bloom_filter#Counting_filters
> Currently, if enough values hash to a bucket, the CountingBloomFilter may begin reporting false negatives when it wraps back around to 0.

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