Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 17 Apr 2012 20:25:17 +0000 (UTC)
From: "Yuki Morishita (Updated) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <541261099.34562.1334694317693.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1969204850.3434.1329898611887.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-3946) BulkRecordWriter shouldn't stream
 any empty data/index files that might be created at end of flush
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yuki Morishita updated CASSANDRA-3946:
--------------------------------------

    Attachment: 3946-1.0.txt

Patch for 1.0 branch attached.
                
> BulkRecordWriter shouldn't stream any empty data/index files that might be created at end of flush
> --------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3946
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3946
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Chris Goffinet
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 1.1.1
>
>         Attachments: 0001-Abort-SSTableWriter-when-exception-occured.patch, 0001-CASSANDRA-3946-BulkRecordWriter-shouldn-t-stream-any.patch, 3946-1.0.txt
>
>
> If by chance, we flush sstables during BulkRecordWriter (we have seen it happen), I want to make sure we don't try to stream them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira