[jira] [Updated] (CASSANDRA-5492) Backport row-level bloom filter removal to 1.2
[ https://issues.apache.org/jira/browse/CASSANDRA-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire updated CASSANDRA-5492: Labels: qa-resolved (was: ) > Backport row-level bloom filter removal to 1.2 > -- > > Key: CASSANDRA-5492 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5492 > Project: Cassandra > Issue Type: Improvement > Components: Core >Affects Versions: 1.2.0 >Reporter: Jonathan Ellis >Assignee: Jonathan Ellis >Priority: Minor > Labels: qa-resolved > Fix For: 1.2.6 > > > With the possible presence of range tombstones, it is erroneous to skip > checking for a given column in SSTableNamesIterator because the bloom filter > says it is not there. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CASSANDRA-5492) Backport row-level bloom filter removal to 1.2
[ https://issues.apache.org/jira/browse/CASSANDRA-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5492: -- Tester: enigmacurry > Backport row-level bloom filter removal to 1.2 > -- > > Key: CASSANDRA-5492 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5492 > Project: Cassandra > Issue Type: Improvement > Components: Core >Affects Versions: 1.2.0 >Reporter: Jonathan Ellis >Assignee: Jonathan Ellis >Priority: Minor > Fix For: 1.2.5 > > > With the possible presence of range tombstones, it is erroneous to skip > checking for a given column in SSTableNamesIterator because the bloom filter > says it is not there. -- 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
[jira] [Updated] (CASSANDRA-5492) Backport row-level bloom filter removal to 1.2
[ https://issues.apache.org/jira/browse/CASSANDRA-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5492: -- Reviewer: slebresne (was: jasobrown) New version on top of current 1.2 (including revert of CASSANDRA-5487) pushed to http://github.com/jbellis/cassandra/commits/5492-3. > Backport row-level bloom filter removal to 1.2 > -- > > Key: CASSANDRA-5492 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5492 > Project: Cassandra > Issue Type: Improvement > Components: Core >Affects Versions: 1.2.0 >Reporter: Jonathan Ellis >Assignee: Jonathan Ellis >Priority: Minor > Fix For: 1.2.5 > > > With the possible presence of range tombstones, it is erroneous to skip > checking for a given column in SSTableNamesIterator because the bloom filter > says it is not there. -- 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
[jira] [Updated] (CASSANDRA-5492) Backport row-level bloom filter removal to 1.2
[ https://issues.apache.org/jira/browse/CASSANDRA-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5492: -- Description: With the possible presence of range tombstones, it is erroneous to skip checking for a given column in SSTableNamesIterator because the bloom filter says it is not there. was: With the possible presence of range tombstones, it is erroneous to skip checking for a given column in SSTableNamesIterator because the bloom filter says it is not there. This is fixed by CASSANDRA-5487, which ignores the BF, but it's a shame to leave unused bloom filters cluttering up the row cache. If it's too risky to do a full backport we can just substitute an AlwaysPresentFilter in RIE.create, but I think the code removal is fairly straightforward. > Backport row-level bloom filter removal to 1.2 > -- > > Key: CASSANDRA-5492 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5492 > Project: Cassandra > Issue Type: Improvement > Components: Core >Affects Versions: 1.2.0 >Reporter: Jonathan Ellis >Assignee: Jonathan Ellis >Priority: Minor > Fix For: 1.2.5 > > > With the possible presence of range tombstones, it is erroneous to skip > checking for a given column in SSTableNamesIterator because the bloom filter > says it is not there. -- 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
