TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Show HN: BoomFilters – Probabilistic data structures for processing streams

70 pointsby tylertreatabout 10 years ago

5 comments

hurinabout 10 years ago
<i>&#x2F;&#x2F; The InverseBloomFilter may report a false negative but can never report a false positive.</i><p>This is actually not true and not possible. There is a good explanation here: <a href="http:&#x2F;&#x2F;cstheory.stackexchange.com&#x2F;a&#x2F;14455&#x2F;43" rel="nofollow">http:&#x2F;&#x2F;cstheory.stackexchange.com&#x2F;a&#x2F;14455&#x2F;43</a><p>There will be a low probability of false positives ~ 2^32*k. (Also it&#x27;s not an inverse-bloom filter, it&#x27;s a cache).
评论 #9360704 未加载
评论 #9360730 未加载
评论 #9361229 未加载
评论 #9360744 未加载
wcdolphinabout 10 years ago
That InverseBloomFilter sounds like an LRU cache of hashes. A true inverse bloom filter can be proven to be impossible, sadly.
Analog24about 10 years ago
<i>With enough data, a traditional Bloom filter &quot;fills up&quot;, after which it has a false-positive probability of 1.</i><p>I don&#x27;t think this correct. The false-positive probability wouldn&#x27;t become 1, it&#x27;s just that every query would return positive, regardless if it&#x27;s a true or false positive. I think what you meant to say was that the positive probability is 1, not the false-positive probability.
natchabout 10 years ago
Why does the readme use Boom and Bloom interchangeably? Is it just a typo that for some reason is randomly scattered throughout the document (and in the repo name itself)? Or is there meant to be a difference? I don&#x27;t see anywhere that the difference is explained, if it&#x27;s intentional.
评论 #9360511 未加载
eternalbanabout 10 years ago
You should checkout Tyler&#x27;s blog. Good solid content for the concurrency geeks.