[ https://issues.apache.org/jira/browse/CASSANDRA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964616#action_12964616 ]
T Jake Luciani commented on CASSANDRA-1555: ------------------------------------------- I'm leaning towards 1) keep both and upgrade to newer impl by performing a major compaction. The problem with 2) is for users with TBs of SSTables and regenerating on startup could take days... > Considerations for larger bloom filters > --------------------------------------- > > Key: CASSANDRA-1555 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1555 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Stu Hood > Assignee: Ryan King > Fix For: 0.8 > > Attachments: cassandra-1555.tgz > > > To (optimally) support SSTables larger than 143 million keys, we need to > support bloom filters larger than 2^31 bits, which java.util.BitSet can't > handle directly. > A few options: > * Switch to a BitSet class which supports 2^31 * 64 bits (Lucene's OpenBitSet) > * Partition the java.util.BitSet behind our current BloomFilter > ** Straightforward bit partitioning: bit N is in bitset N // 2^31 > ** Separate equally sized complete bloom filters for member ranges, which can > be used independently or OR'd together under memory pressure. > All of these options require new approaches to serialization. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.