You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2010/11/03 16:00:30 UTC

[jira] Commented: (CASSANDRA-1702) handle skipping bad rows in LazilyCompacted path

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

Sylvain Lebresne commented on CASSANDRA-1702:
---------------------------------------------

+1

> handle skipping bad rows in LazilyCompacted path
> ------------------------------------------------
>
>                 Key: CASSANDRA-1702
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1702
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: 1702.txt
>
>
> it's easy to handle skipping bad rows during compation in the PreCompacted (merged-in-memory) path and we have done this for a long time.  It is harder in the LazilyCompacted path since we have already started writing data when we discover that some of the source rows cannot be deserialized.  This adds mark/reset to SSTableWriter so compaction can skip back to the beginning in these circumstances.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.