[
https://issues.apache.org/jira/browse/CASSANDRA-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-5487.
---------------------------------------
Resolution: Invalid
Fix Version/s: (was: 2.0)
After talking with Sylvain, I see that the existing code does actually work as
far as row tombstones go -- the idea is, we only consider the columns summary
when determining whether to create an IndexedEntry since if there are
insufficient columns to be worth indexing we're going to seek to the beginning
of the row anyway, so we might as well read the tombstone there as well.
I've reverted this; I'll roll up some of the cleanup here into CASSANDRA-5492
(the bloom filter problem is a legitimate bug).
> Promote row-level tombstones to index file
> ------------------------------------------
>
> Key: CASSANDRA-5487
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5487
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.0
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Attachments: 5487.txt
>
>
> The idea behind promoted indexes (CASSANDRA-2319) was we could skip a seek to
> the row header by keeping the column index in the index file. But, we skip
> writing the row-level tombstone to the index file unless it also has some
> column data. So unless we read the tombstone from the data file (where it is
> guaranteed to exist) we can return incorrect results.
--
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
