cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Assigned) (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-3946) BulkRecordWriter shouldn't stream any empty data/index files that might be created at end of flush
Date Wed, 04 Apr 2012 18:19:26 GMT

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

Jonathan Ellis reassigned CASSANDRA-3946:
-----------------------------------------

    Assignee: Brandon Williams  (was: Chris Goffinet)

Sounds like the right fix here is to make BRW not output zero-length sstables.
                
> 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: Brandon Williams
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: 0001-CASSANDRA-3946-BulkRecordWriter-shouldn-t-stream-any.patch
>
>
> 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

        

Mime
View raw message