Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

A NIF wrapper around a basic bloom filter.

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 c_src
Octocat-spinner-32 ebin Roll ebloom version 2.0 April 11, 2014
Octocat-spinner-32 src Add test which exposes that deserialize() is broken. January 06, 2012
Octocat-spinner-32 .gitignore Add basic .gitignore February 25, 2011
Octocat-spinner-32 .hgignore
Octocat-spinner-32 .hgtags Added tag ebloom-1.0.2 for changeset 7795a460823c September 22, 2010
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 Makefile Use Makefile January 16, 2014
Octocat-spinner-32 Add Travis CI hook and status image. June 28, 2012
Octocat-spinner-32 rebar
Octocat-spinner-32 rebar.config



Travis-CI ::

ebloom is a NIF wrapper around a basic bloom filter.

Quick Start

You must have Erlang/OTP R13B04 or later and a GNU-style build system to compile and run ebloom.

git clone git://
cd ebloom

Start up an Erlang shell with the path to ebloom included.

erl -pa path/to/ebloom/ebin

Create a new bloom filter, insert elements, and test for an elements presence.

1> PredictedElementCount=5.
2> FalsePositiveProbability=0.01.

3> RandomSeed=123.
4> {ok, Ref} = ebloom:new(PredictedElementCount, FalsePositiveProbability, RandomSeed).
5> ebloom:insert(Ref, <<"abcdef">>).
6> true = ebloom:contains(Ref, <<"abcdef">>).
7> false = ebloom:contains(Ref, <<"zzzzzz">>).


We encourage contributions to ebloom from the community.

  1. Fork the ebloom repository on Github.
  2. Clone your fork or add the remote if you already have a clone of the repository.
git clone
# or
git remote add mine
  1. Create a topic branch for your change.
git checkout -b some-topic-branch
  1. Make your change and commit. Use a clear and descriptive commit message, spanning multiple lines if detailed explanation is needed.
  2. Push to your fork of the repository and then send a pull-request through Github.
git push mine some-topic-branch
  1. A Basho engineer or community maintainer will review your patch and merge it into the main repository or send you feedback.
Something went wrong with that request. Please try again.