[
https://issues.apache.org/jira/browse/CASSANDRA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-1063:
--------------------------------------
Attachment: 1063.txt
There's actually a real bug getting masked here -- the correct answer is not
null, but an empty, tombstoned CF.
In fact there are three bugs where we are incorrectly not taking into account
row tombstones:
- we can't just return null if the returnCF is empty, we need to check for
tombstones via removeDeleted
- we can't skip the delete call while building our iterator list, if the
column iterator is empty
- we can't skip deserializing the CF if all the columns in a names predicate
are rejected by the bloom filter
> CFStoreTest has implementation dependent quirks
> -----------------------------------------------
>
> Key: CASSANDRA-1063
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1063
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 0.6, 0.7
>
> Attachments: 0001-Remove-implementation-awareness-from-CFSTest.patch,
> 1063.txt
>
>
> ColumnFamilyStoreTest has two tests that pass due to internal details of the
> API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
