You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/08/12 03:12:16 UTC

[jira] Updated: (CASSANDRA-223) time-based slicing does not work correctly w/ "historial" memtables

     [ https://issues.apache.org/jira/browse/CASSANDRA-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Greene updated CASSANDRA-223:
-------------------------------------

    Component/s: Core

> 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
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.4
>
>         Attachments: 223-2-v2.patch, 223-2.patch, 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.