[
https://issues.apache.org/jira/browse/CASSANDRA-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605891#comment-13605891
]
Jonathan Ellis commented on CASSANDRA-4885:
-------------------------------------------
Here is how I put it in perspective:
If we were writing Cassandra from scratch today, would we include an option to
have row-level BF? No. It might help with some niche workloads but you can
come up with workloads that row cache benefits too. On balance neither was a
good idea, and most of the time if you let people enable them they will make
things worse. Let's put them out of their misery.
> Remove or rework per-row bloom filters
> --------------------------------------
>
> Key: CASSANDRA-4885
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4885
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jason Brown
> Fix For: 2.0
>
> Attachments: 0001-CASSANRDA-4885-Remove-per-row-bloom-filter.patch,
> 0002-CASSANRDA-4885-update-test.patch, 4885-v1.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: http://www.atlassian.com/software/jira
