Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <27589126.253671296175606801.JavaMail.jira@thor>
Date: Thu, 27 Jan 2011 19:46:46 -0500 (EST)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-2059) SSTableDeletingReference only
 deletes data files
In-Reply-To: <27299734.217661296055784226.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on CASSANDRA-2059:
-----------------------------------

Integrated in Cassandra-0.7 #224 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/224/])
    fix deletionof sstable non-data components
patch by jbellis; reviewed by stuhood for CASSANDRA-2059


> SSTableDeletingReference only deletes data files
> ------------------------------------------------
>
>                 Key: CASSANDRA-2059
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2059
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.7.2
>
>         Attachments: 2059.txt
>
>
> Ching-Cheng Chen reports on the mailing list:
> 	
> In SSTableDeletingReference, it try this operation
> components.remove(Component.DATA);
> before
> STable.delete(desc, components);
> However, the components was reference to the components object which was created inside SSTable by
> this.components = Collections.unmodifiableSet(dataComponents);
> As you can see, you can't try the remove operation on that components object.

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