[
https://issues.apache.org/jira/browse/CASSANDRA-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717749#action_12717749
]
Jun Rao commented on CASSANDRA-223:
-----------------------------------
The assumption that columns in an SSTable with a larger file name always have
more recent timestamp also breaks in the following cases:
1. after SSTables are compacted (since the compaction works on a group of
SSTables at a time)
2. hinted data is delivered
3. columns fixed through read repairs
> time-based slicing does not work correctly w/ "historial" memtables
> -------------------------------------------------------------------
>
> Key: CASSANDRA-223
> URL: https://issues.apache.org/jira/browse/CASSANDRA-223
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Attachments: 223.patch
>
>
> TimeFilter assumes that it is done as soon as it finds a column stamped
> earlier than what it is filtering on, but when you have a group of
> "historical" memtables whose columns were written in an arbitrary order this
> is not a safe assumption.
> It is not even a safe assumption when dealing with a single memtable +
> sstable pair, as the attached new test shows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
