Hi Tyler,
I tried what you said and false positives look much more reasonable there.
Thanks for looking into this.
-Chris
- Original Message -
From: "Tyler Hobbs"
To: user@cassandra.apache.org
Sent: Friday, December 19, 2014 1:25:29 PM
Subject: Re: High Bloom Filter FP Rat
I took a look at the code where the bloom filter true/false positive
counters are updated and notice that the true-positive count isn't being
updated on key cache hits:
https://issues.apache.org/jira/browse/CASSANDRA-8525. That may explain
your ratios.
Can you try querying for a few non-existent
We're seeing similar behavior except our FP ratio is closer to 1.0 (100%).
We're using Cassandra 2.1.2.
Schema
---
CREATE TABLE contacts.contact (
id bigint,
property_id int,
created_at bigint,
updated_at bigint,
Hi,
I have create the following table with bloom_filter_fp_chance=0.01:
CREATE TABLE logged_event (
time_key bigint,
partition_key_randomizer int,
resource_uuid timeuuid,
event_json text,
event_type text,
field_error_list map,
javascript_timestamp timestamp,
javascript_uuid uuid,
