[
https://issues.apache.org/jira/browse/CASSANDRA-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-4116:
---------------------------------------
Attachment: CASSANDRA-4116-Set-SSTable-maxTimestamp-correctly-1.0.txt
Added version of patch 0002 with fix to sstable maxTimeStamp against 1.0 branch
> check most recent TS values in SSTables when a row tombstone has already been
> encountered
> -----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4116
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4116
> Project: Cassandra
> Issue Type: Bug
> Reporter: Matthew F. Dennis
> Assignee: Sam Tunnicliffe
> Fix For: 1.2
>
> Attachments:
> CASSANDRA-4116-Set-SSTable-maxTimestamp-correctly-1.0.txt,
> v1-0001-CASSANDRA-4116-After-Row-tombstone-skip-earlier-SSTabl.txt,
> v1-0002-CASSANDRA-4116-Set-SSTable-maxTimestamp-correctly-for-.txt
>
>
> once C* comes across a row tombstone, C* should check the TS on the tombstone
> against all SSTables. If the most recent TS in an SST is older than the row
> tombstone, that entire SST (or the remainder of it) can be safely ignored.
> There are two drivers for this.
> * avoid checking column values that could not possibly be in the result set
> * avoid OOMing because all the tombstones are temporarily kept in memory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
