cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4885) Remove or rework per-row bloom filters
Date Fri, 30 Nov 2012 19:33:58 GMT


Sylvain Lebresne commented on CASSANDRA-4885:

bq. But I still think it should default to off

I agree. And that's also why I'm not sure we should try to be too smart here because the usefulness
of the BF depends more on how the table is used than of how the schema look like. As said
above, I'd be in favor of a columnBF_FP_chance with a default to off since 1) it similar to
our current row BF tunable so it will be familiar to users and 2) it's fine-grained which
cannot hurt. But open to discussion, just seem the best option so far to me.
> Remove or rework per-row bloom filters
> --------------------------------------
>                 Key: CASSANDRA-4885
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jason Brown
>             Fix For: 1.3
>         Attachments: 0001-CASSANRDA-4885-Remove-per-row-bloom-filter.patch, 0002-CASSANRDA-4885-update-test.patch
> Per-row bloom filters may be a misfeature.
> On small rows we don't create them.
> On large rows we essentially only do slice queries that can't take advantage of it.
> And on very large rows if we ever did deserialize it, the performance hit of doing so
would outweigh the benefit of skipping the actual read.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message