cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2349) Expring columns can expire between the two phase of LazilyCompactedRow.
Date Mon, 21 Mar 2011 22:17:06 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009442#comment-13009442
] 

Hudson commented on CASSANDRA-2349:
-----------------------------------

Integrated in Cassandra-0.7 #397 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/397/])
    

> Expring columns can expire between the two phase of LazilyCompactedRow.
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-2349
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2349
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>             Fix For: 0.7.5
>
>         Attachments: 0001-Introduce-expireBefore-and-keep-it-constant-all-thro.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> LazilyCompactedRow reads the columns to compact twice. First to create the index, bloom
filter and calculate the data size, and then another phase to actually write the columns.
But a column can expire between those two phase, which will result in a bad data size in the
sstable (and a possibly corrupted row index).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message