You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2019/04/22 19:52:00 UTC

[jira] [Resolved] (ACCUMULO-320) Introduce better bloom filter

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

Christopher Tubbs resolved ACCUMULO-320.
----------------------------------------
    Resolution: Not A Problem

This is quite old, and there doesn't seem to have been any interest in pursuing this. If this is still an issue that somebody wishes to pursue, please open an issue on GitHub, where we now track issues: https://github.com/apache/accumulo/issues

> Introduce better bloom filter
> -----------------------------
>
>                 Key: ACCUMULO-320
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-320
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: John Vines
>            Priority: Major
>
> The current dynamic filter works by having an array of filters which grows as the filters reach 50% capacity (I believe). This functions, but creates an excessive amount of overhead relative to some other bloom filter techniques. We should look into alternative bloom filter implementations, probably some form of a compacting bloom filter. We should look into HBases' implementation, the hadoop 0.23 implementation, or possibly some other open source implementations which are already available.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)